Difference between revisions of "Crash logs"
Line 1: | Line 1: | ||
{{KBmaster | {{KBmaster}} | ||
== What are diagnostic logs? == | == What are diagnostic logs? == | ||
Line 15: | Line 15: | ||
In addition, platform specifics: | In addition, platform specifics: | ||
== Mac == | === Mac === | ||
In addition to the Viewer's own crash reporting, there's also: | In addition to the Viewer's own crash reporting, there's also: |
Revision as of 08:32, 26 July 2010
What are diagnostic logs?
Diagnostic logs, including crash logs, are a very important tool for debugging Second Life Viewer problems; they allow a developer to try to fix a bug that they've never personally witnessed.
Sometimes, our Support team will ask you to provide diagnostic logs while helping you with a support ticket. Support may ask you to provide specific logs; preferably, you can attach them to a support ticket, or if the contents are shorter, you can open them up in a text editor and copy-and-paste them into your ticket. If you're not sure, ask Support to clarify.
The Viewer can automatically submit crash logs to Linden Lab when the Viewer crashes, but external developers can't see them publicly. If you'd like the broader community to help find the bug that caused Second Life to crash on your computer, you can report the bug on the Issue Tracker and attach your crash logs.
Where do I find the logs?
You'll need to locate the SecondLife
folder which contains the logs
folder, and its location depends on your platform. See the "User settings" page for instructions.
In addition, platform specifics:
Mac
In addition to the Viewer's own crash reporting, there's also:
- A general Mac OS X tool called Crash Reporter. More technical details.
- A System Profiler report, which contains all of the necessary data about your computer and the hardware inside of it. This is useful for Linden Lab to group problems with similar hardware.
- In the Finder, choose Apple menu > About This Mac.
- Click the More Info button to open the System Profiler.
- In the System Profile, choose File > Save. Give the file a unique name so you can find it later, then attach it to your Issue Tracker bug report. Also see "Bug Reporting Best Practices" from Apple.