Difference between revisions of "Crash logs"

From Second Life Wiki
Jump to navigation Jump to search
Line 1: Line 1:
{{KBmaster}} {{TOCright}}
{{KBmaster}} {{TOCright}}


== What are crash logs? ==
== What are diagnostic logs? ==


Crash logs are a very important tool for debugging Second Life Viewer crashes; they allow a developer to try to fix a bug that they've never personally witnessed. Sometimes, our [http://secondlife.com/support Support] team will ask you to provide diagnostic logs while helping you with a support ticket.
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 [http://secondlife.com/support 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.
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.


The exact data you need to attach depends on the platform:
== Where do I find the logs? ==
 
* Mac: Please attach two files to the JIRA report
** the crash log, which will usually be called "Second Life.crash.log", and will be located in ~/Library/Logs/CrashReporter. If you'd prefer, you can search Spotlight for "CrashReporter"; it will be one of the Folder matches. (For a technical discussion of the contents of this file, refer to http://developer.apple.com/technotes/tn2004/tn2123.html)
** a System Profiler report, which contains all of the necessary data about your computer and the hardware inside of it, so that we may group problems with similar hardware together. From the Apple menu, go to About This Mac, then click on More Info. This will open the System Profiler utility; select File -> Save as, pick a name for the file, save it, and then attach it to your JIRA report. (See also http://developer.apple.com/bugreporter/bugbestpractices.html#SP)
 
* Windows:
Attach after crash and before next login to Jira report
 
Main Hard Drive-> Document and Settings-> HP_Administrator(depends on make)-> Application Data-> Second Life-> Logs->SecondLifeCrashReport
 
If Application Data can not be found you need to enable Hidden Folders in Tools-> Folder Options-> View
 
* Linux:
:The crash report is saved at: /home/<username>/.secondlife/logs/SecondLifeCrashReport.log
 
== See also ==


* '''[[User settings]]''' - Check this page if you need help getting to one of the above nested folders.
You'll need to locate the <code>SecondLife</code> folder which contains the <code>logs</code> folder, and its location depends on your platform. '''[[User settings|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 [http://en.wikipedia.org/wiki/Crash_Reporter_%28Mac_OS_X%29 Crash Reporter]. [http://developer.apple.com/technotes/tn2004/tn2123.html More technical details.]
* A [http://en.wikipedia.org/wiki/System_Profiler_%28Apple%29 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 [http://developer.apple.com/bugreporter/bugbestpractices.html "Bug Reporting Best Practices" from Apple].


==On a Windows PC==
It'll usually be in a directory like this:
'''C:\Documents and Settings\''[YOUR USERNAME]''\Application Data\SecondLife\logs'''
Your drive letter may vary depending on your setup, but C: is the most common. To get here, you can also do the following:
# Click the Taskbar's '''Start''' button.
# Select '''Run...'''
# Type "%appdata%" and click '''OK'''.
# Scroll down and look for the SecondLife folder.
# Open the logs folder.
===Vista===
'''Start&gt;Computer&gt;Local disk C:\users&gt;(user name)\AppData&gt;Roaming\Secondlife&gt;Logs'''
Your drive letter may vary depending on your setup, but C: is the most common. To get here, you can also do the following:
# Click the Taskbar's '''Start''' button.
# Select '''Computer''' from the pop up menu.
# Double click on the local disk ('''C:''') drive. # Select '''Users'''
# Select '''username'''
# Select '''appdata'''
# Select '''Roaming'''
# Scroll down and look for the SecondLife folder.
# Open the logs folder.
==On a Mac==
It'll usually be in a directory like this:
'''''[YOUR USERNAME]/''Library/Application Support/SecondLife/logs'''
=='''On Linux'''==
The '''SecondLife.log''' file is located on Linux in:
'''~/.secondlife/logs'''
where '''~''' is your home/user directory.
Please note that "username" refers to the username used on your computer, ''not'' your Second Life Resident name.
We 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, please ask us to clarify.
If you're asked to send crash logs, for future reference, these can be done automatically. In Second Life, '''Preferences &gt; General tab &gt; Crash reports''' should be set to '''Always send''' or '''Ask before sending.'''
[[Category:Error Messages]]
[[Category:Error Messages]]
[[Category:Troubleshooting]]
[[Category:Troubleshooting]]
Line 87: Line 30:
[[Category:General Help]]
[[Category:General Help]]
[[Category:General Second Life Software Information]]
[[Category:General Second Life Software Information]]
[[Category:Knowledge Base]]
[[Category:Knowledge Base]]

Revision as of 09:31, 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.
    1. In the Finder, choose Apple menu > About This Mac.
    2. Click the More Info button to open the System Profiler.
    3. 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.