XDarwin 4.2.0.1 Crashed Spontaneously
Brought to you by:
torrey
Menu
▾
▴
#215 XDarwin 4.2.0.1 Crashed Spontaneously
While working in XDarwin 4.2.0.1 in rootless mode in OS X 10.2.1
today with the following processes/windows:
- Mwm
- Four xterms
- FrameMaker 6.0 running remotely from Solaris 8
XDarwin spontaneously crashed. The incident prompted the crash
was moving the pointer focus from a FrameMaker window to one
of the xterms. The window focus moved in that the window frame
highlight changed; however, the xterm cursor didn't go from an
outline to a solid block. So I moved the pointer back to frame and
back to the xterm. The minute it hit the xterm again and the
window refocused, everything crashed.
The log:
**********
Date/Time: 2002-10-25 11:18:19 -0700
OS Version: 10.2.1 (Build 6D52)
Host: metallurgy.local.
Command: XDarwin
PID: 408
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at
0x0000005b
Thread 0 Crashed:
#0 0x91a97920 in SetCCursor
#1 0x907f0868 in __NSFireMachPort
#2 0x9015c3e4 in __CFMachPortPerform
#3 0x9015c250 in __CFRunLoopDoSource1
#4 0x90149354 in __CFRunLoopRun
#5 0x9018157c in CFRunLoopRunSpecific
#6 0x92ba34cc in RunCurrentEventLoopInMode
#7 0x92bb32f4 in ReceiveNextEventCommon
#8 0x92bda280 in BlockUntilNextEventMatchingListInMode
#9 0x93082184 in _DPSNextEvent
#10 0x930ccf84 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
#11 0x930ca500 in -[NSApplication run]
#12 0x930d2598 in NSApplicationMain
#13 0x00003034 in DarwinHandleGUI
#14 0x00007ec8 in main
#15 0x00002c50 in _start (crt.c:267)
#16 0x00002ad0 in start
Thread 1:
#0 0x90025e8c in select
#1 0x0005fedc in WaitForSomething
#2 0x000289ac in Dispatch
#3 0x0000856c in main
#4 0x000075a0 in -[Xserver run]
#5 0x9081cd38 in forkThreadForFunction
#6 0x90021428 in _pthread_body
PPC Thread State:
srr0: 0x91a97920 srr1: 0x0000f030 vrsave:
0x00000000
xer: 0x00000000 lr: 0x91a97918 ctr: 0x9005e9b8 mq:
0x00000000
r0: 0x91a97918 r1: 0xbfffec40 r2: 0x937a7e10 r3:
0x00c183b4
r4: 0x00000000 r5: 0x00000003 r6: 0x00000030 r7:
0x00000a03
r8: 0x00472010 r9: 0xffffffff r10: 0x00472290 r11:
0xa00042f8
r12: 0x9005e9b8 r13: 0x00000000 r14: 0x00000000 r15:
0x00000001
r16: 0x00000001 r17: 0x00000000 r18: 0x24002280 r19:
0x00000000
r20: 0x000054a3 r21: 0x00000000 r22: 0x003c80c8 r23:
0xbffff334
r24: 0xa1a57670 r25: 0x00c183b4 r26: 0x00c183e8 r27:
0x41800000
r28: 0xa1a50078 r29: 0x41600000 r30: 0x00c183a8 r31:
0x91a97670
Logged In: YES
user_id=133579
Closing this bug as a duplicate of 622186. Please confirm whether this problem is still present in XDarwin 1.1.1.1/XFree86 4.2.1.1.