Xclearcase Kills XDarwin
Brought to you by:
torrey
Menu
▾
▴
#141 Xclearcase Kills XDarwin
I have a consistent crash using a tool called
Xclearcase in rootless mode. This is a X-Windows
GUI to the configuration management tool
"Clearcase" by Rational. This only seems to crash
in rootless mode but is repeatable. I'm connecting
to an SGI. Here is the crash log. (This is the first
bug I've submitted so If there is some other
information I'm missing, I can add that) I'm running
on a dual 450 G4 system with 2 ATI 128 video
cards and 640 MEG of ram.:
Date/Time: 2001-12-04 07:44:56 -0500
OS Version: 10.1.1 (Build 5M28)
Command: XDarwin
PID: 27201
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at
0x04172984
Thread 0:
#0 0x70001308 in mach_msg_overwrite_trap
#1 0x70006394 in mach_msg
#2 0x7017bebc in __CFRunLoopRun
#3 0x701b6ba0 in CFRunLoopRunSpecific
#4 0x7017b804 in CFRunLoopRunInMode
#5 0x7312d614 in
RunEventLoopInModeUntilEventArrives
#6 0x7314056c in ReceiveNextEventCommon
#7 0x73171340 in
BlockUntilNextEventMatchingListInMode
#8 0x70bd70b8 in _DPSNextEvent
#9 0x70bfe5d8 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue
:]
#10 0x70c23468 in -[NSApplication run]
#11 0x70c91ed0 in NSApplicationMain
#12 0x00002768 in DarwinHandleGUI
#13 0x000028e0 in main
#14 0x0000253c in _start
#15 0x0000236c in start
Thread 1:
#0 0x0004af5c in fbBlt
#1 0x0004bb14 in fbBltStip
#2 0x0005473c in fbGetImage
#3 0x000cdeb0 in miSpriteGetImage
#4 0x0026ab90 in RootlessGetImage
#5 0x00062f08 in XineramaGetImageData
#6 0x0006a4c8 in PanoramiXCopyArea
#7 0x0001b9ec in Dispatch
#8 0x00002f04 in main
#9 0x00266c00 in -[Xserver run]
#10 0x70842358 in forkThreadForFunction
#11 0x70020efc in _pthread_body
Thread 2:
#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: 0x0004af5c srr1: 0x0000d030
vrsave: 0x00000000
xer: 0x00000004 lr: 0x0004aa68 ctr:
0x00054558 mq: 0x00000000
r0: 0x00000c88 r1: 0x02031860 r2:
0x03f025a8 r3: 0x0000000b
r4: 0x00000322 r5: 0x00000000 r6:
0x04172984 r7: 0x03e66140
r8: 0x00000000 r9: 0x00000014 r10:
0x00000000 r11: 0x002e4188
r12: 0x00000004 r13: 0x00000000 r14:
0x00000033 r15: 0x0005f610
r16: 0x00000001 r17: 0x80160e88 r18:
0x0005bcb8 r19: 0x00002203
r20: 0x00000000 r21: 0x0000001c r22:
0x70004bc4 r23: 0x70004c58
r24: 0x7016b214 r25: 0x006bac3c r26:
0x8081ab5c r27: 0xc0d19400
r28: 0x00000000 r29: 0xbfffef00 r30:
0x00000000 r31: 0x00000001
**********
Logged In: YES
user_id=398341
Okay, binary-3 crashes in a new and different place
with the same files used with Acroread on IRIX. Here
you go:
Date/Time: 2001-12-12 10:01:25 -0800
OS Version: 10.1.1 (Build 5M28)
Command: XDarwin
PID: 25473
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at
0x00000020
Thread 0:
#0 0x70001308 in mach_msg_overwrite_trap
#1 0x70006454 in mach_msg
#2 0x7017bebc in __CFRunLoopRun
#3 0x701b6ba0 in CFRunLoopRunSpecific
#4 0x7017b804 in CFRunLoopRunInMode
#5 0x7312d614 in
RunEventLoopInModeUntilEventArrives
#6 0x7314056c in ReceiveNextEventCommon
#7 0x73171340 in
BlockUntilNextEventMatchingListInMode
#8 0x70bd70b8 in _DPSNextEvent
#9 0x70bfe5d8 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
#10 0x70c23468 in -[NSApplication run]
#11 0x70c91ed0 in NSApplicationMain
#12 0x00002bc0 in DarwinHandleGUI
#13 0x00002e2c in main
#14 0x0000290c in _start
#15 0x0000273c in start
Thread 1:
#0 0x0008dd9c in fbPutZImage
#1 0x0008dd00 in fbPutImage
#2 0x0002e84c in ProcPutImage
#3 0x000be440 in PanoramiXPutImage
#4 0x00029620 in Dispatch
#5 0x00003678 in main
#6 0x0046ec68 in -[Xserver run]
#7 0x70842358 in forkThreadForFunction
#8 0x70020efc in _pthread_body
PPC Thread State:
srr0: 0x0008dd9c srr1: 0x0000d030 vrsave:
0x00000000
xer: 0x00000004 lr: 0x0008dd2c ctr: 0x0008d794
mq: 0x00000000
r0: 0x00000000 r1: 0x0315fb00 r2: 0x042335a0
r3: 0x040e69e0
r4: 0x040e6a0c r5: 0x00000003 r6: 0xffffffff r7:
0x00000055
r8: 0x000000b5 r9: 0x00000000 r10: 0x0059e7b4
r11: 0x00000000
r12: 0x0008d794 r13: 0x00000000 r14: 0x00000036
r15: 0x0004a010
r16: 0xbfffee70 r17: 0x00000000 r18: 0x00000014
r19: 0x00006e0b
r20: 0x00000000 r21: 0x0000001c r22: 0x70004bc4
r23: 0x70004c58
r24: 0x00000001 r25: 0x0004b060 r26: 0x00000000
r27: 0x02771c00
r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000
r31: 0x00000001
Logged In: YES
user_id=37183
Looks like the bug is more pervasive than I thought. Given the apparent source of the problems, I'm surprised multi-screen mode ever worked at all.
Logged In: YES
user_id=37183
Bugs #488868 and #491920 have exposed fatal flaws in the current Xinerama implementation, so I've rewritten our multi-monitor support from scratch. A replacement XDarwin.app is at http://www.sealiesoftware.com/xdarwin-newxinerama.dmg.gz . It will probably fix this problem too. The new code needs lots of testing if it is going to make it into XFree86 4.2; please test it if you can and file bugs if you find them.
In the new XDarwin's startup output, you'll see "Screen 0 added" only once, no matter how many screens you have. You should instead see one "PseudoramiX screen 0 added" for each real monitor you have.
Logged In: YES
user_id=393399
No crash!. I tried the latest and things are working well so
far. The only visible difference is windows now
occassionally open under the menubar. I'm also using
WindowMaker so one it's icons get's hidden under the menu
bar but that's pretty minor for me.
I won't have access to my multi-monitor mac for a couple
weeks so I won't be able to run any more tests till next
year but I'll keep running with this. Nice job gparker!
Logged In: YES
user_id=398341
I, too, am using the latest version (dec 17) and it is
behaving quite nicely. I've thrown everything that caused
previous versions to crash at it and have yet to get a
crash. Excellent work! I'll keep hammering away at it...
Logged In: YES
user_id=133579
XDarwin 1.0.6 includes this fix. Please make sure this
version also works as it includes the final code (with some
small modifications) that will be part of XFree86 4.2.