Re: Logs?



David Empson <dempson@xxxxxxxxxxxxx> wrote:

Peter James <pfjames2000@xxxxxxxxxxxxxx> wrote:

Occassionally, like any computer a program on my G5 iMac Power PC
crashes. There's usually not a problem in restarting the program, but I
would like to know why this has happened. I understand that the log
will tell me this,

Sort of. It provides detailed technical information about the current
state of the application when the crash occurred, and the technical
reason for the crash (which is almost always a memory access violation).

This can be used by the author of the application to track down bugs,
but apart from some general clues there isn't usually much that an end
user can do with it.

On rare occasions it might give you enough information to identify
something which you can avoid doing in future to prevent further
crashes, but you may need a high degree of technical knowledge (or
assistance from someone else here) to be able to draw this sort of
conclusion.

So my questions are, and please make allowances for a Mac newbie.

1. Does every program have its own log file?

The system creates a separate "crash log" file for each application,
which records details about each time that application crashed.

(It actually maintains a set of these for each user account, so the
crash log you see will only record crashes that occur when you were
running an application, not while another user on the computer was
running the same application.)

2. Is every time the program is called into use appear on the log?

There isn't a general log which tracks normal use of each application.

3. Are all the logs located in the same directory, and if so where is
it?

The best way to see them is to use the Console application, which is
located in /Applications/Utilities. It lets you browse through all
available logs on the computer in a reasonably safe and easy to use
manner.

The crash logs are stored here:

~/Library/Logs/CrashReporter

(That's the Library folder inside your home folder.)

There is a separate file for each application, which has the name of the
application followed by ".crash.log" (or sometimes just ".crash"). They
are plain text files.

Console also shows you lots of other logs. The ones of main interest are
the "Console log" (described as "Console Messages" under the "LOG
DATABASE QUERIES" heading in 10.5) and "system.log".

The Console Messages log contains diagnostic messages output by many
applications, which are sometimes useful in getting clues about
problems. system.log contains similar information, sometimes in greater
detail.

I have been having a lot of trouble with Safari 3.1.1 running under
10.5.3 on an Intel mini. It doesn't exactly crash. It just sort of
becomes increasingly non-functional. For example, it will not give a
link cursor for a known link, and if I click the link anyway, it does
nothing. When I try to quit it - it won't. I have to force quit it.
It doesn't say anything like non-responding in the force quit panel. I
have tried to find a log and send it to Jolly Roger, but I can't find
anything in the logs. Any ideas?

TIA


--
Never believe anything until it's officially denied.
.



Relevant Pages

  • Re: Word 2004 crashes when cutting text - FIXED!!!
    ... Hey Tony, these frequent quits or Crashes that you get, would it be possible ... for you to send me directly the text file of your Crash Log? ... Mac Word Test ...
    (microsoft.public.mac.office.word)
  • Re: Excel 2004 Version 11.5.5 (090512) & OS 10.6.1 Crashes
    ... your reportage certainly met our needs :-) ... The "Blue Screen" crashes on certain particular key combinations are Finder ... Re starting Excel ... am find with posting the crash log but you will need to advise how to ...
    (microsoft.public.mac.office.excel)
  • Re: Logs?
    ... crashes, but you may need a high degree of technical knowledge (or ... The system creates a separate "crash log" file for each application, ... which records details about each time that application crashed. ... Console also shows you lots of other logs. ...
    (comp.sys.mac.system)
  • System_service_exception error on vista
    ... and i hit yes to display crash log and it doesn't pop anything up. ... getting a crash log if it crashes again. ... I used the registry mechanic to look through my event logs. ... some of the error's it reported multiple times since install: ...
    (microsoft.public.windows.vista.performance_maintenance)
  • Re: preventing dos window close upon program termination
    ... While debugging, the call stack certainly serves my purposes, and is far ... Normally, if a program crashes, the debugger will stop and show you ... Seeing all the console outputs is not reliable if the program crashes. ... The console window WILL close when the program ...
    (microsoft.public.vsnet.debugging)

Loading