Re: strange crash report

FROM : Christopher Wolf
DATE : Wed Nov 20 09:39:08 2002

On Tuesday, November 19, 2002, at 11:31 PM, Mark Steinberg wrote:

> I have gotten this 7 or 8 times in the last two months.
>
> Any ideas?


CrashReporter isn't infallible... gathering information from a dying
process is tricky and there are times when a process self-destructs in
such a way that it's impossible for CrashReporter to generate a
complete crash-report.

If CrashReporter can not figure out the name or owner of the dying
process then the crash log gets written to
/Library/Logs/CrashReporter/???.crash.log... (the theory is that some
information is better than none and the pid or the symbol information
in the backtrace combined with user observations may still offer enough
clues to determine which process it was that died)  In these cases
it's likely that CrashReporter also will be unable to succesfully
forward the mach exception to the original mach exception handler for
the process.... the rest of the console spew reflects various non-fatal
errors resulting from this situation.

In other situations crash-reporter may be able to get the process
name/owner information but may be unable to generate a backtrace for
the process... in these cases you will see a crash report with the
"Backtrace not available" message.

  If you have *reproducible* cases of either of these on 10.2 Jaguar
then please file a bug-report with Apple!  (Non-reproducible reports
of this are not particularly useful.)

- Chris


> Console:
> RegisterProcess failed (error = -2805)
> Nov 19 22:54:54 embro crashdump: Crash report written to:
> /Library/Logs/CrashReporter/???.crash.log
>
> Nov 19 22:54:54 embro crashdump: getpwuid("878983200") failed
>
> Nov 19 22:54:54 embro /usr/libexec/crashreporterd: exception_raise()
> failed forwarding exception: (os/kern) invalid argument
>
> Nov 19 22:54:54 embro /usr/libexec/crashreporterd: newport: 2603
> originalport: b07 thread: 2307 task: 2207 exception: 1
>
> Nov 19 22:54:54 embro /usr/libexec/crashreporterd: mach_msg() reply
> failed: (ipc/send) invalid destination port
>
> Crash Log:
> **********
>
> Date/Time:  2002-11-19 22:54:54 -0500
> OS Version: 10.2.2 (Build 6F21)
> Host:      embro.homeip.net
>
> Command:    Unknown
> PID:        1131
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
>
> Backtrace not available
>
> PPC Thread State:
>  srr0: 0x9005d4d8 srr1: 0x0000d030                vrsave: 0x00000000
>    xer: 0x00000000  lr: 0x9005d4d4  ctr: 0x9001bae0  mq: 0x00000000
>    r0: 0x00000025  r1: 0xf0407780  r2: 0x72203d20  r3: 0x0000046b
>    r4: 0x00000000  r5: 0x00000000  r6: 0xf0407760  r7: 0x73746572
>    r8: 0x50726f63  r9: 0x00000000  r10: 0x6661696c  r11: 0xa000441c
>    r12: 0x9001bae0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
>    r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
>    r20: 0x0005ace0  r21: 0x00000001  r22: 0x0005adc8  r23: 0x0005adc0
>    r24: 0x00000000  r25: 0x0006b940  r26: 0x00000000  r27: 0xa30010f4
>    r28: 0x00000000  r29: 0x0000046b  r30: 0x00000000  r31: 0x9005d470
>
> I think it might have to do with Application Enhancer from Unsanity
> since one of the crash logs looked like this:
>
> **********
>
> Date/Time:  2002-09-23 16:44:26 -0400
> OS Version: 10.2.1 (Build 6D51)
> Host:      embro.homeip.net
>
> Command:    Unknown
> PID:        527
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000003
>
> Thread 0 Crashed:
>  #0  0x002b8f98 in 0x2b8f98
>  #1  0x002b9230 in 0x2b9230
>  #2  0x0025e5dc in 0x25e5dc
>  #3  0x0025e65c in 0x25e65c
>  #4  0x002b8664 in 0x2b8664
>  #5  0x002bafb8 in 0x2bafb8
>  #6  0x002bd068 in 0x2bd068
>  #7  0x002bcf68 in 0x2bcf68
>  #8  0x002bb9a8 in 0x2bb9a8
>  #9  0x002bbbf4 in 0x2bbbf4
>  #10  0x002b7ef0 in 0x2b7ef0
>  #11  0x001d9e8c in 0x1d9e8c
>  #12  0x90279260 in CCFM_LaunchApplication
>  #13  0x0000362c in main
>  #14  0x0000329c in _start
>  #15  0x0000311c in start
>
> Thread 1:
>  #0  0x90074328 in mach_msg_trap
>  #1  0x90006670 in mach_msg
>  #2  0xc00076cc in __ape_internal
>  #3  0xc0000dd0 in __ape_agent
>  #4  0x90021428 in _pthread_body
>
> PPC Thread State:
>  srr0: 0x002b8f98 srr1: 0x0200d030                vrsave: 0x00000000
>    xer: 0x00000000  lr: 0x002b8f70  ctr: 0x00000000  mq: 0x00000000
>    r0: 0x00000000  r1: 0xbffff710  r2: 0x0044b000  r3: 0x7c000000
>    r4: 0xbffffea0  r5: 0x00000000  r6: 0x00000003  r7: 0x00000038
>    r8: 0x0000000c  r9: 0xffffffff  r10: 0xa1b1c1d3  r11: 0x0000007f
>    r12: 0x00000000  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
>    r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
>    r20: 0x00047540  r21: 0xffffffff  r22: 0xbffffc80  r23: 0x00000000
>    r24: 0x00000000  r25: 0x00000008  r26: 0x00000000  r27: 0x00000000
>    r28: 0x00573a31  r29: 0x005ef040  r30: 0x00482320  r31: 0x01d3d778
>
> Anybody seen anything like this?
>
> Mark
> --
> Mark Steinberg
> Textile Technologies LLC
> http://www.textiletech.com