#166 xdarwin hang up

open
nobody
None
5
2002-02-11
2002-02-11
Anonymous
No

I'm using xdarwin on rootless mode with four monitors.
I have a trouble of xdarwin hang-up sometimes. I'm not sure why this
happen. The following is the crash log.

Date/Time: 2002-02-04 21:53:53 +0900
OS Version: 10.1.2 (Build 5P48)

Command: XDarwin
PID: 16231

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x0b40c5b8

Thread 0:
#0 0x7003f4c8 in semaphore_wait_signal_trap
#1 0x7003f2c8 in _pthread_cond_wait
#2 0x70816bc4 in -[NSRecursiveLock lock]
#3 0x0026d69c in -[Xserver applicationWillTerminate:]
#4 0x708374a8 in _nsNotificationCenterCallBack
#5 0x7019be7c in _postNotification
#6 0x70199600 in _CFNotificationCenterPostLocalNotification
#7 0x70199324 in _CFNotificationCenterPostNotification
#8 0x7082c2e0 in -[NSNotificationCenter
postNotificationName:object:userInfo:flags:]
#9 0x70833c14 in -[NSNotificationCenter postNotificationName:object:]
#10 0x70c369b4 in -[NSApplication terminate:]
#11 0x70833b28 in -[NSObject performSelector:withObject:]
#12 0x70c94698 in -[NSApplication sendAction:to:from:]
#13 0x70bf9d7c in -[NSMenu performActionForItemAtIndex:]
#14 0x70c1d638 in -[NSCarbonMenuImpl
performActionWithHighlightingForItemAtIndex:]
#15 0x70c392a4 in _NSHandleCarbonMenuEvent
#16 0x70bd72cc in _DPSNextEvent
#17 0x70bfe5d8 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
#18 0x70c23468 in -[NSApplication run]
#19 0x70c91ed0 in NSApplicationMain
#20 0x0000259c in DarwinHandleGUI
#21 0x00002714 in main
#22 0x00002370 in _start
#23 0x000021a0 in start

Thread 1:
#0 0x70003370 in free_list_remove_ptr
#1 0x70003078 in szone_free
#2 0x70002e10 in malloc_zone_free
#3 0x70002aa4 in free
#4 0x00034a60 in Xfree
#5 0x000d464c in miMarkUnrealizedWindow
#6 0x0001648c in UnrealizeTree
#7 0x00016650 in UnmapWindow
#8 0x00012fcc in DeleteWindow
#9 0x00023fe8 in FreeClientResources
#10 0x000222dc in CloseDownClient
#11 0x000223e8 in KillAllClients
#12 0x0001b8ec in Dispatch
#13 0x00002d38 in main
#14 0x0026e778 in -[Xserver run]
#15 0x70842358 in forkThreadForFunction
#16 0x7002054c in _pthread_body

Thread 2:
#0 0x70000978 in mach_msg_overwrite_trap
#1 0x70005a04 in mach_msg
#2 0x70026a2c in _pthread_become_available
#3 0x70026724 in pthread_exit
#4 0x70020550 in _pthread_body

Thread 3:
#0 0x7003f4c8 in semaphore_wait_signal_trap
#1 0x7003f2c8 in _pthread_cond_wait
#2 0x7086c34c in -[NSConditionLock lockWhenCondition:]
#3 0x70ba1358 in -[NSUIHeartBeat _heartBeatThread:]
#4 0x70842358 in forkThreadForFunction
#5 0x7002054c in _pthread_body

PPC Thread State:
srr0: 0x70003370 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x00000004 lr: 0x70003344 ctr: 0x700056b0 mq:
0x00000000
r0: 0x0000003f r1: 0x0461e870 r2: 0x0b5a41a8 r3: 0x003eb010
r4: 0x0b40c5b0 r5: 0x0000070b r6: 0x00323dd8 r7: 0x00323dd8
r8: 0x045be710 r9: 0x00000000 r10: 0x0ad77010 r11:
0x800036f0
r12: 0x700056b0 r13: 0x00000000 r14: 0x00000033 r15:
0x01639f60
r16: 0x01639f90 r17: 0xbfffee90 r18: 0x01162f80 r19: 0x00002b07
r20: 0x00000000 r21: 0x0000001c r22: 0x70004234 r23:
0x700042c8
r24: 0x00000004 r25: 0x000003a4 r26: 0x70002d84 r27:
0x70002e10
r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000 r31: 0x00000001

**********

Discussion

  • Torrey T. Lyons

    Torrey T. Lyons - 2002-02-12

    Logged In: YES
    user_id=133579

    First, you should note which version of XDarwin you are
    using. I'm guessing from the stack trace you are using
    XDarwin 1.1.

    Second, from the stack trace you were quitting XDarwin at
    the time it crashed. Was this intended? XDarwin will rarely
    crash on quitting. My guess is that this is due to an
    earlier memory smasher that happens to cause problems when
    quitting. If you were not trying to quit, what were you
    doing and what clients were you using?

     
  • Nobody/Anonymous

    Logged In: NO

    Thanks for reply.

    >First, you should note which version of XDarwin you are
    >using. I'm guessing from the stack trace you are using
    >XDarwin 1.1.
    Yes, I'm using XDarwin1.1.

    >Second, from the stack trace you were quitting XDarwin at
    >the time it crashed. Was this intended? XDarwin will rarely
    >crash on quitting. My guess is that this is due to an
    >earlier memory smasher that happens to cause problems when
    >quitting.
    I did not intended to quit.

    >If you were not trying to quit, what were you
    >doing and what clients were you using?
    I did nothring at that time. But XDarwin was freezed.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks