{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Toby Paterson <[EMAIL PROTECTED]>
>> No code has changed in the jabber code in a LONG time. Can you get a
>> backtrace from gdb or turn on crash reporter and get a crash report?
>
> This has happened consistently twice today. I select "Disconnect" from
> the Jabber icon, and wait for it to say Offline, then "Connect", and it
> crashes. This is the Fire.crash.log:
>
> Date/Time: 2001-12-18 09:46:25 -0500
> OS Version: 10.1.1 (Build 5M28)
> Host: gibbon.urbanape.com
>
> Command: Fire
> PID: 1825
>
> Exception: EXC_BAD_ACCESS (0x0001)
> Codes: KERN_INVALID_ADDRESS (0x0001) at 0xc8636ba4
>
> Thread 0 Crashed:
> #0 0x02a1193c in -[JABBERCommunicationController
> executeRunLoopCheck:]
> #1 0x708d06e8 in __NSFireTimer
> #2 0x70196984 in __CFRunLoopDoTimer
> #3 0x7017c17c in __CFRunLoopRun
> #4 0x701b6ba0 in CFRunLoopRunSpecific
> #5 0x7017b804 in CFRunLoopRunInMode
> #6 0x7312d614 in RunEventLoopInModeUntilEventArrives
> #7 0x731404f8 in ReceiveNextEventCommon
> #8 0x73171340 in BlockUntilNextEventMatchingListInMode
> #9 0x70bd70b8 in _DPSNextEvent
> #10 0x70bfe5d8 in -[NSApplication
> nextEventMatchingMask:untilDate:inMode:dequeue:]
> #11 0x70c23468 in -[NSApplication run]
> #12 0x70c91ed0 in NSApplicationMain
> #13 0x00036018 in main
> #14 0x000049d0 in _start
> #15 0x00004800 in start
>
> Thread 1:
> #0 0x70001308 in mach_msg_overwrite_trap
> #1 0x70006394 in mach_msg
> #2 0x700273dc in _pthread_become_available
> #3 0x700270d4 in pthread_exit
> #4 0x70020f00 in _pthread_body
>
> PPC Thread State:
> srr0: 0x02a1193c srr1: 0x0000f030 vrsave: 0x00000000
> xer: 0x00000004 lr: 0x02a11900 ctr: 0x00000000 mq: 0x00000000
> r0: 0x08638000 r1: 0xbfffeb60 r2: 0x031abed0 r3: 0xbfffec20
> r4: 0x00000004 r5: 0x00000000 r6: 0x00000001 r7: 0x00000000
> r8: 0x00000001 r9: 0xbfffeba4 r10: 0xbfffeba4 r11: 0x08638000
> r12: 0x00000000 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
> r16: 0x00000001 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
> r20: 0xbffff0e8 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
> r24: 0x01f589c0 r25: 0x01f6cea0 r26: 0x01f524a0 r27: 0x01e12a80
> r28: 0x01e1be90 r29: 0x0218e000 r30: 0xbfffeb60 r31: 0x02a11870
>
I've seen the exact same thing with a crash in the exact same place
under different circumstances: while connected to jabber, I put my
machine to sleep and then wake it up. When the timer fires after
wakeup, it invariably dies trying to deference through current->conn->fd
in -executeRunLoopCheck: The conn field in one of the JABBER_Conn nodes
is garbage. In fact, the whole struct looks like garbage.
X
{#} ----------------------------------------------------+[ fire ]+---
