where are the diagnostic reports, or why aren't there any?

Question

esa ceduti Author

Level 1

5 points

where are the diagnostic reports, or why aren't there any?

Hello

I understand that under mavericks, diagnostic reports are supposed to be found either in

/Library/Logs/DiagnosticReports/ (System Diagnostic Reports),

or in

~/Library/Logs/DiagnosticReports (User Diagnostic Reports).

Unfortunately, even after a number of crashes, they aren't. While in my case, the system DiagnosticReports folder exists, but contains nothing but powerstats, in the user library, not even the folder is there.

So, either they are elsewhere, or they aren't being generated. In the first case, my question would be: Where are the diagnostic reports? In the latter, it would be: Why aren't there any (despite the system crashes)?

(A similar question is to be found here: https://discussions.apple.com/thread/5871067?answerId=24773940022#24773940022 , but ended with an open question. I'm starting a new thread, because this old one is marked as answered.)

Thanks a lot.

Mac Pro, OS X Mountain Lion, 6 GB 1066 MHz DDR3 Memory, ATI Radeon HD 4870

Posted on Feb 14, 2014 7:22 AM

Reply

Answer 1

esa ceduti Author

Level 1

5 points

Feb 14, 2014 10:49 AM in response to Tony T1

Yes, that's quite clear. But a system not responding with no solution but holding down the power button is clearly an issue should create a diagnostic report, isn't it? So I guess the one question out of the two remaining is: Why doesn't my mac write a diagnostic report?

Reply

Answer 2

Feb 14, 2014 7:37 AM in response to esa ceduti

Switch to the Finder and hold down the option key while clicking on the Go menu to expose your User / Library folder.

Reply

Answer 3

esa ceduti Author

Level 1

5 points

Feb 14, 2014 9:14 AM in response to QuickTimeKirk

Well, I do have access to the User Library (in fact, I've set the finder to display all hidden files to be sure I don't miss an otherwise hidden DiagnosticReport file). The absent folder I was refering to is the DiagnosticReports folder inside the Logs folder within the User Library (~/Library/Logs/DiagnosticReports : no such folder).

Reply

Answer 4

Tony T1

Level 6

10,244 points

Feb 14, 2014 9:24 AM in response to esa ceduti

Open Console (in Applications/Utilities)

Logs will be written by Apps when there's a probem and/or the App crashes,

otherwise no logs will be written

Reply

Answer 5

esa ceduti Author

Level 1

5 points

Feb 14, 2014 10:22 AM in response to Tony T1

Console displays what's in the folders, too: powerstats. Nothing to do with crash logs. So, same two questions remaining: Either, the last crashes are reported elsewhere (form what I understand, that seems unlikely), or they aren't generated in the first place—but why? And what to do about it?

Reply

Answer 6

Tony T1

Level 6

10,244 points

Feb 14, 2014 10:29 AM in response to esa ceduti

These are logs to help if a program crashes, or has other issues.

If there are no issues, no logs are produced.

See: http://support.apple.com/kb/ht4063

Diagnostic and usage reports may include the following information:

Details about application or system not responding, application unexpectedly quitting, or kernel panics
Information about events on your computer (for example, whether a certain function, such as waking your computer, was successful or not)
Usage information (for example, data about how you use Apple and third-party software, hardware, and services)

Here's an example of one of my DiagnosticLogs:

Process: Preview [799]

Path: /Applications/Preview.app/Contents/MacOS/Preview

Identifier: com.apple.Preview

Version: 7.0 (826)

Build Info: Preview-826000000000000~2

Code Type: X86-64 (Native)

Parent Process: launchd [159]

Responsible: Preview [799]

User ID: 501

Date/Time: 2014-02-13 20:34:49.464 -0500

OS Version: Mac OS X 10.9.1 (13B42)

Report Version: 11

Anonymous UUID: 1B59A7FC-F3E6-021D-3D42-C1AE03E74EA3

Sleep/Wake UUID: 465C3455-1DE9-4244-9DFC-41A34BC596F5

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 0 beyond bounds for empty array'

terminating with uncaught exception of type NSException

abort() called

Reply