Home Page Forums MAME Non-Windows MAME Support SDLMAME and X-Arcade = crash

Print Thread

Page 1 of 12

…

SDLMAME and X-Arcade = crash #45984 11/02/08 12:41 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Ok, new problem... My shiny brand new X-Arcade Tankstick seems to be working fine in the OS (10.5.5) (every key is responding, registered in system profiler) But as soon as I launch SDLMAME (0.128u1), it just hang there, eating 100% of one processor core. Force quit has no effect. Nothing to do except restarting the MacPro. Same result if I launch from MameTunes. Can't post the crashing report: too big...

Re: SDLMAME and X-Arcade = crash Marc Mame #45985 11/02/08 01:08 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	This is what I got when I run a mame -v Not much... Code Last login: Sun Nov 2 01:47:26 on ttys000 bgnxx-x-xx-xx-xx-xx:~ MarcV$ /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u1/mame -v Parsing mame.ini Parsing mame.ini Setting SDL_VIDEO_GL_DRIVER = '/System/Library/Frameworks/OpenGL.framework/Libraries/libGL.dylib' ...

Re: SDLMAME and X-Arcade = crash Marc Mame #45986 11/02/08 01:13 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I also remember that I've trashed AppleHIDMouseAgent.plugin and AirPortUserAgent.plugin from sys/lib/UserEventPlugin since it (AppleHIDMouseAgent) was source of pb with X-Arcade. (as told on their web site)

Re: SDLMAME and X-Arcade = crash Marc Mame #46008 11/02/08 06:33 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Does no one use an X-Arcade with OSX SDLMAME ? Any thought why SDLMAME crash with X-Acrade ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46011 11/02/08 08:45 PM
Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA M MAMEBase Senior Member
MAMEBase Senior Member M Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA	Unfortunately, I don't know enough about the inner workings of the X-Arcade to be able to offer any real advice... Is this device seen as a keyboard by OSX, and if so, could your french keymap setings be interfering with it? The following statement is true... The preceding statement is false.

Re: SDLMAME and X-Arcade = crash MAMEBase #46016 11/02/08 11:01 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	The device is seen as an X-Arcade device (namely) by Mac OS Sys-Info It act as a keyboard (you actualy can type in TextEdit) I don't think my french keymap setting as anything to do since SDL hang way before it got there. I was hoping Mr Belmont would have a clue... Thank for your support though Dave...

Re: SDLMAME and X-Arcade = crash Marc Mame #46018 11/02/08 11:16 PM
Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA M MAMEBase Senior Member
MAMEBase Senior Member M Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA	Just curious... What happens if you disconnect your keyboard (leaving the X-Arcade attached), and launch using MAMETunes with the Easy settings enabled? Last edited by MAMEBase; 11/02/08 11:22 PM. The following statement is true... The preceding statement is false.

Re: SDLMAME and X-Arcade = crash MAMEBase #46020 11/02/08 11:42 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Just did it : same thing. MameTunes launch fine but as soon as I launch a game, SDLMAME hangs. No window, nothing. You should know that it works perfectly with MAME OS X (0.124) I've no idea what to do next...

Re: SDLMAME and X-Arcade = crash Marc Mame #46021 11/03/08 12:35 AM
Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA M MAMEBase Senior Member
MAMEBase Senior Member M Joined: Sep 2000 Posts: 481 Likes: 2 Madison, WI, USA	Well, I'm afraid I'm stumped as well... I would suggest a google search for 'x arcade in mame' to see if there may be another forum that might be able to provide you with an answer... This may be useful as well - http://www.xgaming.com/service/how-to-x-arcade-mame-mac.shtml Last edited by MAMEBase; 11/03/08 12:37 AM. The following statement is true... The preceding statement is false.

Re: SDLMAME and X-Arcade = crash MAMEBase #46022 11/03/08 12:53 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I have already spent hours on the net but nothing close to this pb... I may drop a mail to X-Gaming support... Who knows... Thanks for your precious help and support Dave. It's really sad having this baby just sitting there...

Re: SDLMAME and X-Arcade = crash Marc Mame #46024 11/03/08 01:14 AM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	I've got nothing. I have no idea how a keyboard could lock up SDLMAME that early.

Re: SDLMAME and X-Arcade = crash R. Belmont #46026 11/03/08 01:43 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	That's it. I'm gonna cry now.... Anyway, thanks for your input Richard. Would that help if you had a look at the crashing report ? (it's fairly big)

Re: SDLMAME and X-Arcade = crash Marc Mame #46027 11/03/08 01:57 AM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Possibly. If it's actually crashing it'd be more helpful if you could rebuild from scratch with SYMBOLS=1 and then do a GDB backtrace: % gdb mame gdb> run pacman (or whatever you do) [crash] gdb> bt [copy/paste what's printed after this to a post].

Re: SDLMAME and X-Arcade = crash R. Belmont #46028 11/03/08 02:23 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Actually it's not really crashing since it hang. But after trying to force quit a few times (from activity monitor) I eventualy get a crashing report from the MacOS finder. I'll try to rebuild like you said. Just to be sure, something like that : make -j3 SYMBOLS=1 TARGETOS=macosx ? Not sure what to do next with that GDB backtrace...

Re: SDLMAME and X-Arcade = crash Marc Mame #46029 11/03/08 02:28 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	In the mean time, I'll try to split the crash report : Part 1/2 [code]Date/Time: 2008-11-02 01:21:24 +0100 OS Version: 10.5.5 (Build 9F33) Architecture: i386 Report Version: 4 Command: mame Path: /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u1/mame Version: ??? (???) Parent: launchd [1] PID: 261 Event: hang Time: 36.42s Steps: 287 Process: mame [261] Path: /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u1/mame ADDRESS BINARY 00001000 /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u1/mame 02ca8000 /Library/Frameworks/SDL.framework/Versions/A/SDL 27cdc000 /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib Thread id: 80626b0 User stack: 287 start + 54 (in mame) [0x2466] 287 _main + 1568 (in mame) [0x5d54b0] 287 -[NSApplication run] + 795 (in AppKit) [0x922a6cdb] 287 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 287 __DPSNextEvent + 1189 (in AppKit) [0x922ae601] 287 _AEProcessAppleEvent + 38 (in HIToolbox) [0x96bc5b61] 287 _aeProcessAppleEvent + 177 (in AE) [0x96b66425] 287 __Z25dispatchEventAndSendReplyPK6AEDescPS_ + 44 (in AE) [0x96b6657e] 287 __Z20aeDispatchAppleEventPK6AEDescPS_mPh + 144 (in AE) [0x96b66648] 287 __NSAppleEventManagerGenericHandler + 223 (in Foundation) [0x9437c50f] 287 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 655 (in Foundation) [0x9437c7ff] 287 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 98 (in AppKit) [0x922b0d10] 287 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 284 (in AppKit) [0x922b1517] 287 -[NSApplication _sendFinishLaunchingNotification] + 77 (in AppKit) [0x92337971] 287 -[NSApplication _postDidFinishNotification] + 125 (in AppKit) [0x92337a62] 287 -[NSNotificationCenter postNotificationName:object:] + 56 (in Foundation) [0x9435dc88] 287 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128 (in Foundation) [0x94354440] 287 __CFXNotificationPostNotification + 179 (in CoreFoundation) [0x9386fd93] 287 ___CFXNotificationPost + 362 (in CoreFoundation) [0x9386faba] 287 __nsnote_callback + 106 (in Foundation) [0x943571da] 287 -[SDLMain applicationDidFinishLaunching:] + 76 (in mame) [0x5d4d1c] 287 _SDL_main + 46 (in mame) [0x5a271e] 287 _cli_execute + 1093 (in mame) [0x5e3055] 287 _mame_execute + 1717 (in mame) [0x61e705] 287 _osd_init + 252 (in mame) [0x5a285c] 287 _SDL_Init + 23 (in SDL) [0x2cd9e67] 287 _SDL_InitSubSystem + 206 (in SDL) [0x2cd9dbe] 287 _SDL_CDEject + 177 (in SDL) [0x2cdaf51] 287 _SDL_SoftStretch + 2969 (in SDL) [0x2cdc959] 287 _IORegistryEntryCreateCFProperties + 38 (in IOKit) [0x91caa3da] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 287 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 287 _mach_msg_overwrite_trap + 752 [0x126257] 287 _ipc_kobject_server + 247 [0x12d17e] 287 _IOMapPages + 2166 [0x1880a3] 287 _is_io_registry_entry_get_properties + 106 [0x43aab4] 287 __ZNK9IOService19serializePropertiesEP11OSSerialize + 25 [0x40e49b] 287 __ZNK15IORegistryEntry19serializePropertiesEP11OSSerialize + 76 [0x40ab86] 287 __ZNK12OSDictionary9serializeEP11OSSerialize + 305 [0x3ef201] 287 __ZNK7OSArray9serializeEP11OSSerialize + 88 [0x3ec638] 287 com.apple.iokit.IOHIDFamily (1.5.3) + 43160 [0xc16898] 287 __ZNK12OSDictionary9serializeEP11OSSerialize + 305 [0x3ef201] 287 __ZNK7OSArray9serializeEP11OSSerialize + 88 [0x3ec638] 286 com.apple.iokit.IOHIDFamily (1.5.3) + 43160 [0xc16898] 254 __ZNK12OSDictionary9serializeEP11OSSerialize + 305 [0x3ef201] 171 __ZNK8OSNumber9serializeEP11OSSerialize + 36 [0x3efcf0] 44 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 53 [0x3eed25] 41 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 65 [0x3eeaf1] 27 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 36 [0x3eed14] 26 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 58 [0x3eeaea] 20 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 48 [0x3eeae0] 13 __ZN11OSSerialize20previouslySerializedEPK15OSMetaClassBase + 193 [0x3f12b3] 9 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 98 [0x3eeb12] 5 __ZN12OSDictionary14ensureCapacityEj + 136 [0x3eea30] 5 _kfree + 65 [0x12fb15] 5 _kmem_free + 120 [0x164699] 5 _vm_map_remove + 145 [0x16a437] 5 _vm_map_simplify + 3475 [0x169bdf] 2 _vm_fault_unwire + 479 [0x16352a] 2 _thread_cancel_timer + 132 [0x134c63] 2 _vm_fault_unwire + 691 [0x1635fe] 2 _vm_fault_cleanup + 79 [0x15f022] 1 _lck_rw_done_gen + 19 [0x19da3c] 1 _ml_set_interrupts_enabled + 9 [0x1a2363] 1 _lck_rw_done_gen + 160 [0x19dac9] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 _vm_fault_unwire + 357 [0x1634b0] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 4 __ZN12OSDictionary14ensureCapacityEj + 60 [0x3ee9e4] 4 _kalloc + 25 [0x12fa72] 4 _kalloc_canblock + 86 [0x12f9f7] 4 _kmem_alloc + 56 [0x1640d8] 3 _kernel_memory_allocate + 990 [0x163fbc] 3 _vm_map_protect + 3200 [0x16d89a] 3 _vm_fault_wire + 192 [0x163736] 2 _vm_fault_wire_fast + 576 [0x160106] 1 _OSAddAtomic + 13 [0x3ffaea] 1 _pmap_enter + 4 [0x195fb1] 1 _lck_rw_lock_shared + 20 [0x19a7e4] 1 _kernel_memory_allocate + 715 [0x163ea9] 1 _vm_page_alloc + 26 [0x17fe6c] 1 __enable_preemption + 17 [0x19b7e1] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 4 _bcopy + 28 [0x19807c] 80 __ZNK8OSNumber9serializeEP11OSSerialize + 102 [0x3efd32] 32 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 53 [0x3eed25] 31 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 36 [0x3eed14] 8 __ZN11OSSerialize14addXMLStartTagEPK15OSMetaClassBasePKc + 60 [0x3f1304] 8 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 8 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 5 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 5 _kmem_free + 120 [0x164699] 5 _vm_map_remove + 145 [0x16a437] 4 _vm_map_simplify + 3475 [0x169bdf] 1 _vm_fault_unwire + 691 [0x1635fe] 1 _vm_fault_cleanup + 79 [0x15f022] 1 _lck_rw_done_gen + 160 [0x19dac9] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 _lck_rw_lock_exclusive + 572 [0x19e6da] 1 _mutex_unlock + 88 [0x19ade8] 1 _mutex_lock_spin + 61 [0x19a94d] 1 _vm_map_lookup_entry + 162 [0x1650f6] 3 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 3 _kmem_realloc + 624 [0x164424] 3 _vm_map_protect + 3200 [0x16d89a] 3 _vm_fault_wire + 192 [0x163736] 2 _vm_fault_wire_fast + 576 [0x160106] 2 _pmap_enter + 1965 [0x19675a] 1 _vm_fault_wire_fast + 149 [0x15ff5b] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 3 __ZN11OSSerialize14addXMLStartTagEPK15OSMetaClassBasePKc + 83 [0x3f131b] 3 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 3 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 2 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 2 _kmem_realloc + 624 [0x164424] 2 _vm_map_protect + 3200 [0x16d89a] 2 _vm_fault_wire + 192 [0x163736] 1 _mutex_lock_spin + 61 [0x19a94d] 1 _vm_fault_wire_fast + 576 [0x160106] 1 _pmap_enter + 2840 [0x196ac5] 1 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 1 _kmem_free + 120 [0x164699] 1 _vm_map_remove + 145 [0x16a437] 1 _vm_map_simplify + 3475 [0x169bdf] 1 _mutex_unlock + 88 [0x19ade8] 3 __ZN11OSSerialize14addXMLStartTagEPK15OSMetaClassBasePKc + 136 [0x3f1350] 3 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 3 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 3 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 3 _kmem_realloc + 624 [0x164424] 3 _vm_map_protect + 3200 [0x16d89a] 2 _vm_fault_wire + 192 [0x163736] 1 _vm_fault_wire_fast + 576 [0x160106] 1 _pmap_enter + 2411 [0x196918] 1 _hw_lock_unlock + 17 [0x19a671] 1 _vm_fault_wire_fast + 152 [0x15ff5e] 2 __ZN11OSSerialize14addXMLStartTagEPK15OSMetaClassBasePKc + 159 [0x3f1367] 2 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 1 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 1 _kmem_realloc + 624 [0x164424] 1 _vm_map_protect + 3200 [0x16d89a] 1 _vm_fault_wire + 192 [0x163736] 1 _vm_fault_wire_fast + 576 [0x160106] 1 _pmap_enter + 2411 [0x196918] 1 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 1 _kmem_free + 120 [0x164699] 1 _vm_map_remove + 145 [0x16a437] 1 _hw_lock_unlock + 59 [0x19a69b] 1 __ZN11OSSerialize14addXMLStartTagEPK15OSMetaClassBasePKc + 34 [0x3f12ea] 1 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 1 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 1 _kmem_free + 120 [0x164699] 1 _vm_map_remove + 145 [0x16a437] 1 _vm_map_simplify + 3475 [0x169bdf] 1 _vm_fault_unwire + 357 [0x1634b0] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 2 __ZNK8OSNumber9serializeEP11OSSerialize + 238 [0x3efdba] 2 __ZN11OSSerialize12addXMLEndTagEPKc + 74 [0x3f13de] 2 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 2 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 1 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 1 _kmem_realloc + 624 [0x164424] 1 _vm_map_protect + 3200 [0x16d89a] 1 _vm_fault_wire + 192 [0x163736] 1 _vm_fault_wire_fast + 688 [0x160176] 1 _lck_rw_done_gen + 160 [0x19dac9] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 1 _kmem_free + 120 [0x164699] 1 _vm_map_remove + 145 [0x16a437] 1 _vm_map_simplify + 3475 [0x169bdf] 1 _vm_fault_unwire + 357 [0x1634b0] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 __ZNK9OSBoolean9serializeEP11OSSerialize + 47 [0x3ecd73] 1 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 1 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 1 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 1 _kmem_realloc + 624 [0x164424] 1 _vm_map_protect + 3200 [0x16d89a] 1 _vm_fault_wire_fast + 691 [0x160179] 11 __ZNK12OSDictionary9serializeEP11OSSerialize + 30 [0x3ef0ee] 6 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 65 [0x3eeaf1] 2 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 58 [0x3eeaea] 1 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 36 [0x3eed14] 1 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 53 [0x3eed25] 1 __ZN12OSDictionary9setObjectEPK8OSSymbolPK15OSMetaClassBase + 48 [0x3eeae0] 8 __ZNK12OSDictionary9serializeEP11OSSerialize + 66 [0x3ef112] 8 __ZNK12OSDictionary9getObjectEPK8OSSymbol + 53 [0x3eed25] 6 __ZNK12OSDictionary9serializeEP11OSSerialize + 248 [0x3ef1c8] 6 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 6 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 6 _kmem_realloc + 624 [0x164424] 6 _vm_map_protect + 3200 [0x16d89a] 6 _vm_fault_wire + 192 [0x163736] 4 _vm_fault_wire_fast + 576 [0x160106] 2 _pmap_enter + 1965 [0x19675a] 1 _pmap_enter + 2037 [0x1967a2] 1 _pmap_enter + 2833 [0x196abe] 1 _mutex_unlock + 88 [0x19ade8] 1 _mutex_unlock + 46 [0x19adbe] 5 __ZNK12OSDictionary9serializeEP11OSSerialize + 279 [0x3ef1e7] 4 __ZN11OSSerialize12addXMLEndTagEPKc + 74 [0x3f13de] 4 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 4 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 3 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 3 _kmem_realloc + 624 [0x164424] 3 _vm_map_protect + 3200 [0x16d89a] 3 _vm_fault_wire + 192 [0x163736] 1 _vm_fault_wire_fast + 576 [0x160106] 1 _vm_fault_enter + 722 [0x15fc0e] 1 _hw_lock_to + 11 [0x19a5fb] 1 _vm_page_lookup + 61 [0x17e25e] 1 _mutex_unlock + 46 [0x19adbe] 1 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 1 _kmem_free + 120 [0x164699] 1 _vm_map_remove + 145 [0x16a437] 1 _vm_map_simplify + 3475 [0x169bdf] 1 _vm_fault_unwire + 691 [0x1635fe] 1 _vm_fault_cleanup + 79 [0x15f022] 1 _lck_rw_done_gen + 160 [0x19dac9] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 __ZN11OSSerialize12addXMLEndTagEPKc + 97 [0x3f13f5] 1 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 1 __ZN11OSSerialize14ensureCapacityEj + 76 [0x3f162c] 1 _kmem_realloc + 624 [0x164424] 1 _vm_map_protect + 3200 [0x16d89a] 1 _vm_fault_wire + 192 [0x163736] 1 _mutex_unlock + 46 [0x19adbe] 2 __ZNK12OSDictionary9serializeEP11OSSerialize + 147 [0x3ef163] 2 __ZN11OSSerialize9addStringEPKc + 42 [0x3f148c] 2 __ZN11OSSerialize7addCharEc + 50 [0x3f143a] 2 __ZN11OSSerialize14ensureCapacityEj + 113 [0x3f1651] 2 _kmem_free + 120 [0x164699] 2 _vm_map_remove + 145 [0x16a437] 1 _vm_fault_unwire + 588 [0x163597] 1 _vm_map_simplify + 3475 [0x169bdf] 1 _mutex_lock_spin + 61 [0x19a94d] 1 com.apple.iokit.IOHIDFamily (1.5.3) + 42628 [0xc16684] Thread id: 80a0ba0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _SDL_SemWait + 49 (in SDL) [0x2ce9341] 287 _SDL_Linked_Version + 397 (in SDL) [0x2cda14d] 287 _mach_wait_until + 10 (in libSystem.B.dylib) [0x950415c6] Kernel stack: 129 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 128 _mach_wait_until_trap + 61 [0x12975d] 128 _thread_block + 33 [0x136ac0] 128 _thread_block_reason + 135 [0x136a1c] 127 _thread_setrun + 3173 [0x135f10] 127 _machine_idle + 278 [0x1a2aab] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 _mach_wait_until_trap + 42 [0x12974a] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 __ZN10IOWorkLoop10threadMainEv + 191 [0x41f809] 1 _thread_block_parameter + 32 [0x136a9d] 1 _thread_block_reason + 157 [0x136a32] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 _i386_astintr + 47 [0x1a7e6c] 1 _ast_taken + 247 [0x1291aa] 1 _bsd_ast + 721 [0x37f2f5] 1 _postsig + 156 [0x37d7c2] 1 _sig_lock_to_exit + 40 [0x37d50b] 1 _task_suspend + 81 [0x13b926] 1 _task_wait_locked + 39 [0x13b8c3] 1 _thread_wait + 161 [0x1372e7] 1 _thread_continue + 1181 [0x136853] Process: ATSServer [125] Path: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer ADDRESS BINARY 00001000 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer Thread id: 67c7128 User stack: 287 ??? [0x4b36] 287 ??? [0xdcf3f] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc0a78 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: Activity Monitor [267] Path: /Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor ADDRESS BINARY 00001000 /Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor 23c5f000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib 23eab000 /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera 4d57d000 /System/Library/PrivateFrameworks/GraphKit.framework/Versions/A/GraphKit ba900000 /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib Thread id: 81b28b8 User stack: 287 ??? [0x1efa] 287 _NSApplicationMain + 574 (in AppKit) [0x92273f14] 272 -[NSApplication run] + 795 (in AppKit) [0x922a6cdb] 272 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 272 __DPSNextEvent + 657 (in AppKit) [0x922ae3ed] 272 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x96bc310d] 270 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 270 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 270 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 266 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 3 _CFRunLoopRunSpecific + 4469 (in CoreFoundation) [0x9388eb45] 3 ___NSFireTimer + 147 (in Foundation) [0x9438c1e3] 2 ??? [0xd034] 2 __CF_forwarding_prep_0 + 50 (in CoreFoundation) [0x9390da12] 2 ____forwarding___ + 986 (in CoreFoundation) [0x9390d9aa] 2 -[NSDistantObject forwardInvocation:] + 329 (in Foundation) [0x9438db89] 1 -[NSConnection sendInvocation:internal:] + 3562 (in Foundation) [0x9438ec3a] 1 -[NSConcretePortCoder decodeReturnValue:] + 360 (in Foundation) [0x943976a8] 1 __NSWalkData2 + 1724 (in Foundation) [0x9438fb0c] 1 -[NSConcretePortCoder decodeRetainedObject] + 282 (in Foundation) [0x943933aa] 1 -[NSDictionary(NSDictionary) initWithCoder:] + 886 (in Foundation) [0x94384eb6] 1 __NSWalkData2 + 1724 (in Foundation) [0x9438fb0c] 1 -[NSConcretePortCoder decodeRetainedObject] + 282 (in Foundation) [0x943933aa] 1 -[NSArray(NSArray) initWithCoder:] + 612 (in Foundation) [0x94364904] 1 __NSWalkData2 + 1724 (in Foundation) [0x9438fb0c] 1 -[NSConcretePortCoder decodeRetainedObject] + 282 (in Foundation) [0x943933aa] 1 -[NSDictionary(NSDictionary) initWithCoder:] + 324 (in Foundation) [0x94384c84] 1 ??? [0xffff0088] 1 -[NSConnection sendInvocation:internal:] + 3005 (in Foundation) [0x9438ea0d] 1 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 ??? [0xcfe2] 1 __CFRelease + 216 (in CoreFoundation) [0x93890788] 1 ___CFDictionaryDeallocate + 281 (in CoreFoundation) [0x9385dd49] 1 __CFRelease + 216 (in CoreFoundation) [0x93890788] 1 ___CFArrayReleaseValues + 221 (in CoreFoundation) [0x9381fa0d] 1 _CFRelease + 0 (in CoreFoundation) [0x93890580] 1 _CFRunLoopRunSpecific + 844 (in CoreFoundation) [0x9388dd1c] 1 ___CFRunLoopDoObservers + 466 (in CoreFoundation) [0x9388c9c2] 1 __handleWindowNeedsDisplay + 436 (in AppKit) [0x922b0548] 1 -[NSWindow displayIfNeeded] + 189 (in AppKit) [0x922b0725] 1 -[NSView displayIfNeeded] + 933 (in AppKit) [0x922b0b77] 1 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3090 (in AppKit) [0x92370117] 1 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 306 (in AppKit) [0x923735f3] 1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4433 (in AppKit) [0x92374b0b] 1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4433 (in AppKit) [0x92374b0b] 1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4433 (in AppKit) [0x92374b0b] 1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 759 (in AppKit) [0x92373cb1] 1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1969 (in AppKit) [0x923756f2] 1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1050 (in AppKit) [0x9237535b] 1 -[NSView _drawRect:clip:] + 3853 (in AppKit) [0x92376864] 1 -[NSTableView drawRect:] + 2199 (in AppKit) [0x922e62d8] 1 -[NSOutlineView drawRowIndexes:clipRect:] + 122 (in AppKit) [0x922e767e] 1 -[NSTableView drawRowIndexes:clipRect:] + 363 (in AppKit) [0x922e77f4] 1 -[NSTableView drawRow:clipRect:] + 872 (in AppKit) [0x9234237a] 1 -[NSOutlineView _drawContentsAtRow:column:withCellFrame:] + 99 (in AppKit) [0x92342db2] 1 -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 269 (in AppKit) [0x92342f19] 1 -[NSTextFieldCell drawWithFrame:inView:] + 818 (in AppKit) [0x922e9297] 1 -[NSTextFieldCell drawInteriorWithFrame:inView:] + 747 (in AppKit) [0x922e96eb] 1 __NSDrawTextCell + 188 (in AppKit) [0x922deccb] 1 _objc_msgSend + 80 (in libobjc.A.dylib) [0x94f6e6c0] 2 _ReceiveNextEventCommon + 175 (in HIToolbox) [0x96bc31d2] 2 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 2 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 1 _CFRunLoopRunSpecific + 844 (in CoreFoundation) [0x9388dd1c] 1 ___CFRunLoopDoObservers + 466 (in CoreFoundation) [0x9388c9c2] 1 __handleWindowNeedsDisplay + 436 (in AppKit) [0x922b0548] 1 -[NSWindow displayIfNeeded] + 189 (in AppKit) [0x922b0725] 1 -[NSView displayIfNeeded] + 933 (in AppKit) [0x922b0b77] 1 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 457 (in AppKit) [0x9236f6ce] 1 -[NSViewHierarchyLock lockForWritingWithExceptionHandler:] + 50 (in AppKit) [0x928c59bb] 1 -[NSViewHierarchyLock _lockForWriting:handler:] + 416 (in AppKit) [0x928c5e0b] 1 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] 1 _CFRunLoopRunSpecific + 4469 (in CoreFoundation) [0x9388eb45] 1 ___NSFireTimer + 147 (in Foundation) [0x9438c1e3] 1 ??? [0xd034] 1 __CF_forwarding_prep_0 + 50 (in CoreFoundation) [0x9390da12] 1 ____forwarding___ + 986 (in CoreFoundation) [0x9390d9aa] 1 -[NSDistantObject forwardInvocation:] + 329 (in Foundation) [0x9438db89] 1 -[NSConnection sendInvocation:internal:] + 3005 (in Foundation) [0x9438ea0d] 1 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 15 -[NSApplication run] + 847 (in AppKit) [0x922a6d0f] 15 -[NSApplication sendEvent:] + 2941 (in AppKit) [0x92349311] 15 -[NSWindow sendEvent:] + 5381 (in AppKit) [0x9237c76b] 9 -[NSControl mouseDown:] + 888 (in AppKit) [0x9237e02c] 9 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 541 (in AppKit) [0x9237e772] 7 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1827 (in AppKit) [0x9237ef1f] 7 -[NSCell _sendActionFrom:] + 169 (in AppKit) [0x9237f8c6] 7 -[NSControl sendAction:to:] + 108 (in AppKit) [0x9237fa40] 7 -[NSApplication sendAction:to:from:] + 112 (in AppKit) [0x9237fb03] 7 -[NSAlert buttonPressed:] + 394 (in AppKit) [0x9251d740] 7 -[NSApplication endSheet:returnCode:] + 288 (in AppKit) [0x923c17fb] 7 -[NSAlert didEndSheet:returnCode:contextInfo:] + 105 (in AppKit) [0x92579ee6] 7 ??? [0x1c0b2] 7 -[NSWindow orderOut:] + 50 (in AppKit) [0x9238047d] 7 -[NSWindow orderWindow:relativeTo:] + 105 (in AppKit) [0x9236bcc8] 7 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 2081 (in AppKit) [0x9236c546] 7 -[NSWindow(NSSheets) _orderOutRelativeToWindow:] + 123 (in AppKit) [0x925139b0] 7 -[NSMoveHelper(NSSheets) _closeSheet:andMoveParent:] + 457 (in AppKit) [0x92513bed] 3 -[NSMoveHelper _doAnimation] + 72 (in AppKit) [0x92511726] 3 -[NSUIHeartBeat disableHeartBeating] + 134 (in AppKit) [0x92511c24] 3 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] 3 -[NSMoveHelper _doAnimation] + 980 (in AppKit) [0x92511ab2] 3 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 2 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _CFRunLoopRunSpecific + 4469 (in CoreFoundation) [0x9388eb45] 1 __NSMoveHelperTimerCallBack + 639 (in AppKit) [0x923b4f74] 1 _CGSReenableUpdate + 32 (in CoreGraphics) [0x90eaed68] 1 _CGSReenableUpdateForConnections + 390 (in CoreGraphics) [0x90eaeef0] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 -[NSMoveHelper _doAnimation] + 1048 (in AppKit) [0x92511af6] 1 -[NSMoveHelper _stopAnimation] + 173 (in AppKit) [0x923b5861] 1 -[NSMoveHelper _releaseEffect] + 25 (in AppKit) [0x92513d34] 1 _MetalSheetRelease + 299 (in CoreGraphics) [0x90f0bb33] 1 _CGSReleaseWindow + 370 (in CoreGraphics) [0x90eadac6] 1 __CGSReleaseWindowList + 452 (in CoreGraphics) [0x90eadc92] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 2 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1179 (in AppKit) [0x9237ec97] 2 -[NSWindow nextEventMatchingMask:] + 102 (in AppKit) [0x9237f4ab] 2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 2 __DPSNextEvent + 657 (in AppKit) [0x922ae3ed] 2 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x96bc310d] 2 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 2 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 2 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 2 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 5 -[NSToolbarItemViewer mouseDown:] + 5076 (in AppKit) [0x924c1ebe] 5 -[NSToolbarButton sendAction] + 88 (in AppKit) [0x924c293d] 5 -[NSToolbarButton sendAction:to:] + 100 (in AppKit) [0x924c29ac] 5 ??? [0x1b762] 5 ??? [0x1c032] 5 _NSBeginAlertSheet + 100 (in AppKit) [0x92579901] 4 __NXDoLocalRunAlertSheet + 1141 (in AppKit) [0x92579d78] 3 -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector:contextInfo:] + 1033 (in AppKit) [0x923adc2f] 3 -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 785 (in AppKit) [0x923ae1c7] 2 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 1566 (in AppKit) [0x9236c343] 2 -[NSWindow(NSSheets) _orderFrontRelativeToWindow:] + 206 (in AppKit) [0x9250fe60] 2 -[NSMoveHelper(NSSheets) _moveParent:andOpenSheet:] + 1764 (in AppKit) [0x92510571] 2 -[NSMoveHelper _doAnimation] + 980 (in AppKit) [0x92511ab2] 2 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _CFRunLoopRunSpecific + 4469 (in CoreFoundation) [0x9388eb45] 1 __NSMoveHelperTimerCallBack + 611 (in AppKit) [0x923b4f58] 1 _MetalSheetProgress + 10770 (in CoreGraphics) [0x90f09e73] 1 _resizeTopShadow + 467 (in CoreGraphics) [0x9112fad6] 1 _CGContextSetGrayFillColor + 257 (in CoreGraphics) [0x90eb937b] 1 _CGGStateSetFillColor + 56 (in CoreGraphics) [0x90e1b02b] 1 _CFRetain + 133 (in CoreFoundation) [0x93890335] 1 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 1354 (in AppKit) [0x9236c26f] 1 -[NSWindow displayIfNeeded] + 189 (in AppKit) [0x922b0725] 1 -[NSView displayIfNeeded] + 933 (in AppKit) [0x922b0b77] 1 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3090 (in AppKit) [0x92370117] 1 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 306 (in AppKit) [0x923735f3] 1 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 759 (in AppKit) [0x92373cb1] 1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1969 (in AppKit) [0x923756f2] 1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1969 (in AppKit) [0x923756f2] 1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1050 (in AppKit) [0x9237535b] 1 -[NSView _drawRect:clip:] + 3853 (in AppKit) [0x92376864] 1 -[NSControl drawRect:] + 378 (in AppKit) [0x922e2b6b] 1 -[NSImageCell drawWithFrame:inView:] + 2230 (in AppKit) [0x9239f557] 1 -[NSImageCell drawInteriorWithFrame:inView:] + 751 (in AppKit) [0x9239f853] 1 -[NSImage _drawMappingAlignmentRectToRect:withState:backgroundStyle:operation:fraction:flip:] + 1041 (in AppKit) [0x927480de] 1 -[NSImage drawInRect:fromRect:operation:fraction:] + 414 (in AppKit) [0x92301aec] 1 -[NSBitmapImageRep _loadData] + 513 (in AppKit) [0x9239b730] 1 _CGImagePlusCreateImage + 491 (in ImageIO) [0x9319de70] 1 _CGDataProviderGetBytePtr + 122 (in CoreGraphics) [0x90e80497] 1 _faultDataAcquireBytePointer + 190 (in CoreGraphics) [0x9116e6e4] 1 _getBandProcICNS + 953 (in ImageIO) [0x931aaff5] 1 -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector:contextInfo:] + 1354 (in AppKit) [0x923add70] 1 -[NSWindow makeKeyWindow] + 72 (in AppKit) [0x923336e1] 1 -[NSWindow _changeKeyAndMainLimitedOK:] + 642 (in AppKit) [0x9233397c] 1 -[NSPanel resignKeyWindow] + 98 (in AppKit) [0x92380cde] 1 -[NSWindow resignKeyWindow] + 436 (in AppKit) [0x92380ead] 1 _changeCursorRects + 447 (in AppKit) [0x9238114f] 1 __NXDiscardCursorRect + 70 (in AppKit) [0x923479d6] 1 _CGSRemoveTrackingArea + 272 (in CoreGraphics) [0x90eb2c0d] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 __NXDoLocalRunAlertSheet + 758 (in AppKit) [0x92579bf9] 1 -[NSAlert buildAlertStyle:title:message:first:second:third:oldStyle:args:] + 236 (in AppKit) [0x9234da52] 1 -[NSAlert buildAlertStyle:title:formattedMsg:first:second:third:oldStyle:] + 6104 (in AppKit) [0x9234f24e] 1 -[NSAlert setTitle:andMessage:] + 374 (in AppKit) [0x92353d63] 1 -[NSScreen frame] + 38 (in AppKit) [0x922812fd] 1 __NXGetScreenRect + 36 (in AppKit) [0x922810a6] 1 _CGSGetDisplayBounds + 47 (in CoreGraphics) [0x90e0c9ac] 1 _updateAllDisplayInfoAsNeeded + 223 (in CoreGraphics) [0x90e0c0f4] 1 _bindDisplayMapping + 416 (in CoreGraphics) [0x90e08b14] 1 _CGSReleaseRegion + 99 (in CoreGraphics) [0x90e0c3b3] 1 __CFRelease + 216 (in CoreFoundation) [0x93890788] 1 _regionFinalize + 40 (in CoreGraphics) [0x90e0c3e8] 1 _szone_free + 115 (in libSystem.B.dylib) [0x950476ad] 1 -[NSOutlineView mouseDown:] + 611 (in AppKit) [0x923d5c55] 1 -[NSTableView mouseDown:] + 741 (in AppKit) [0x923c406a] 1 -[NSTableView _performDragFromMouseDown:] + 282 (in AppKit) [0x923c5f5c] 1 -[NSTableView _dragShouldBeginFromMouseDown:] + 577 (in AppKit) [0x923c68d3] 1 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 1 __DPSNextEvent + 657 (in AppKit) [0x922ae3ed] 1 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x96bc310d] 1 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 1 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 1 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 6 _PE_incoming_interrupt + 131 [0x447f78] 6 _lapic_interrupt + 300 [0x1af933] 6 _sync_iss_to_iks + 114 [0x1a7fa8] 6 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 4 _mach_msg_overwrite_trap + 4783 [0x127216] 4 _ipc_mqueue_receive + 738 [0x120e9e] 4 _thread_block + 33 [0x136ac0] 4 _thread_block_reason + 135 [0x136a1c] 4 _thread_setrun + 3173 [0x135f10] 4 _machine_idle + 278 [0x1a2aab] 1 _mach_msg_overwrite_trap + 2047 [0x126766] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 1 _mach_msg_overwrite_trap + 3771 [0x126e22] 1 _ipc_mqueue_receive + 750 [0x120eaa] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Thread id: 80f7f20 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 810dd60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 81b24f0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _fe_fragment_thread + 54 (in QuartzCore) [0x91f4dbb9] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 81b3048 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _fe_fragment_thread + 54 (in QuartzCore) [0x91f4dbb9] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Kernel stack: 1 _unix_syscall + 572 [0x3ddd6e] 1 ___semwait_signal_nocancel + 187 [0x37c663] 1 _semaphore_wait_signal_trap_internal + 88 [0x13999d] 1 _semaphore_wait_internal + 565 [0x13980a] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Thread id: 80fa8b8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _fe_fragment_thread + 54 (in QuartzCore) [0x91f4dbb9] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 810c2e8 User stack: 225 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 225 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 225 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 225 -[NSThread main] + 45 (in Foundation) [0x94357bad] 187 -[NSUIHeartBeat _heartBeatThread:] + 753 (in AppKit) [0x92314358] 187 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x9439d895] 187 -[NSConditionLock lockWhenCondition:beforeDate:] + 144 (in Foundation) [0x9439d930] 187 -[NSCondition waitUntilDate:] + 236 (in Foundation) [0x9439db1c] 187 _semaphore_timedwait_signal_trap + 10 (in libSystem.B.dylib) [0x95041506] 36 -[NSUIHeartBeat _heartBeatThread:] + 2042 (in AppKit) [0x92314861] 36 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] 2 -[NSUIHeartBeat _heartBeatThread:] + 1011 (in AppKit) [0x9231445a] 2 -[NSWindow(NSWindow_Theme) heartBeat:] + 293 (in AppKit) [0x924616d4] 2 -[NSButtonCell(NSDefaultButtonIndicatorPrivate) heartBeat:] + 2179 (in AppKit) [0x92461fa8] 2 -[NSView _lightWeightRecursiveDisplayInRect:] + 644 (in AppKit) [0x92462494] 2 _CFArrayApplyFunction + 198 (in CoreFoundation) [0x9381dcb6] 2 __lightWeightRecursiveDisplayInRect2 + 335 (in AppKit) [0x92462618] 2 -[NSView _lightWeightRecursiveDisplayInRect:] + 644 (in AppKit) [0x92462494] 2 _CFArrayApplyFunction + 198 (in CoreFoundation) [0x9381dcb6] 2 __lightWeightRecursiveDisplayInRect2 + 335 (in AppKit) [0x92462618] 2 -[NSView _lightWeightRecursiveDisplayInRect:] + 577 (in AppKit) [0x92462451] 2 -[NSView _drawRect:clip:] + 3853 (in AppKit) [0x92376864] 2 -[NSControl drawRect:] + 378 (in AppKit) [0x922e2b6b] 1 -[NSButtonCell drawInteriorWithFrame:inView:] + 2054 (in AppKit) [0x922f9c7d] 1 -[NSButtonCell _configureAndDrawTitleWithRect:cellFrame:controlView:] + 2890 (in AppKit) [0x9267884e] 1 -[NSButtonCell drawTitle:withFrame:inView:] + 187 (in AppKit) [0x923dde0c] 1 -[NSAttributedString(NSStringDrawingExtension) _drawCenteredVerticallyInRect:scrollable:] + 2834 (in AppKit) [0x923de944] 1 _objc_msgSend + 83 (in libobjc.A.dylib) [0x94f6e6c3] 1 -[NSButtonCell drawWithFrame:inView:] + 232 (in AppKit) [0x922f810f] 1 -[NSButtonCell drawBezelWithFrame:inView:] + 152 (in AppKit) [0x922f8398] 1 -[NSButtonCell _coreUIDrawBezelWithFrame:inView:] + 362 (in AppKit) [0x922f88f4] 1 __ZN11CUIRenderer4DrawE6CGRectP9CGContextPK14__CFDictionaryPS5_ + 3122 (in CoreUI) [0x919e1bb2] 1 __ZN11CUIRenderer14DrawPushButtonEPK10CUIContext + 3745 (in CoreUI) [0x919d815d] 1 _CGContextDrawImages + 297 (in CoreGraphics) [0x90e54859] 1 _ripc_DrawImages + 9522 (in libRIP.A.dylib) [0x90db5cb1] 1 _ripc_RenderImage + 273 (in libRIP.A.dylib) [0x90da954d] 1 _ripl_BltImage + 1307 (in libRIP.A.dylib) [0x90dbf97b] 1 _ripl_Mark + 38 (in libRIP.A.dylib) [0x90dbd376] 1 _argb32_image_mark + 9620 (in CoreGraphics) [0x90e61c04] Kernel stack: 2 _PE_incoming_interrupt + 131 [0x447f78] 2 _lapic_interrupt + 300 [0x1af933] 2 _sync_iss_to_iks + 114 [0x1a7fa8] 2 _unix_syscall + 572 [0x3ddd6e] 2 ___semwait_signal_nocancel + 104 [0x37c610] 2 _semaphore_timedwait_trap_internal + 89 [0x139a6d] 2 _semaphore_wait_internal + 565 [0x13980a] 2 _thread_block + 33 [0x136ac0] 2 _thread_block_reason + 135 [0x136a1c] 2 _thread_setrun + 3173 [0x135f10] 2 _machine_idle + 278 [0x1a2aab] Process: AirPort Base Station Agent [119] Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent ADDRESS BINARY 00001000 /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent Thread id: 6cbf790 User stack: 287 ??? [0x1dca] 287 _NSApplicationMain + 574 (in AppKit) [0x92273f14] 287 -[NSApplication run] + 795 (in AppKit) [0x922a6cdb] 287 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 287 __DPSNextEvent + 657 (in AppKit) [0x922ae3ed] 287 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x96bc310d] 287 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 287 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: AppleSpell [190] Path: /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell ADDRESS BINARY 00001000 /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell 000e4000 /usr/lib/liblangid.dylib Thread id: 80f8e40 User stack: 287 ??? [0x1f22] 287 ??? [0x2229] 287 -[NSSpellServer run] + 198 (in Foundation) [0x943cf186] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: DirectoryService [33] Path: /usr/sbin/DirectoryService ADDRESS BINARY 00001000 /usr/sbin/DirectoryService 00160000 /System/Library/PrivateFrameworks/DirectoryServiceCore.framework/Versions/A/DirectoryServiceCore Thread id: 67c7c80 User stack: 287 start + 54 (in DirectoryService) [0x16912] 287 _main + 2767 (in DirectoryService) [0x173ff] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 67c4b58 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 287 __ZN9DSCThread3RunEv + 39 (in DirectoryServiceCore) [0x167f83] 287 __ZN20CPluginRunLoopThread10ThreadMainEv + 222 (in DirectoryService) [0x235bc] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 67c8410 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 287 __ZN9DSCThread3RunEv + 39 (in DirectoryServiceCore) [0x167f83] 287 __ZN17CMigHandlerThread10ThreadMainEv + 303 (in DirectoryService) [0x237f5] 271 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 16 _mach_msg_server + 343 (in libSystem.B.dylib) [0x950b6ed3] 16 _DSlibinfoMIG_server + 109 (in DirectoryService) [0x99b83] 16 __XQuery + 343 (in DirectoryService) [0x99e26] 16 _libinfoDSmig_do_Query + 585 (in DirectoryService) [0x2f3ad] 16 __ZN12CCachePlugin20ProcessLookupRequestEiPcii + 638 (in DirectoryService) [0x952fa] 16 __ZN12CCachePlugin13DSgetnameinfoEP7kvbuf_ti + 2142 (in DirectoryService) [0x8dfa0] 16 _idna_dns_lookup + 572 (in DirectoryService) [0xcf5f4] 16 _dns_lookup_soa_min + 215 (in libresolv.9.dylib) [0x9026e32b] 16 __sdns_search + 832 (in libresolv.9.dylib) [0x90269d56] 16 __pdns_query + 223 (in libresolv.9.dylib) [0x90269a03] 16 _res_nquery_soa_min + 356 (in libresolv.9.dylib) [0x90280785] 16 _res_9_nsend_2 + 65 (in libresolv.9.dylib) [0x902840a3] 16 _dns_res_send + 4332 (in libresolv.9.dylib) [0x90283de7] 16 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Kernel stack: 271 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 271 _mach_msg_overwrite_trap + 3771 [0x126e22] 271 _ipc_mqueue_receive + 750 [0x120eaa] 271 _thread_block + 33 [0x136ac0] 271 _thread_continue + 1181 [0x136853] Thread id: 6952998 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 8062a78 User stack: 218 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 218 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 218 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 218 _syscall + 5 (in libSystem.B.dylib) [0x950841d5] Thread id: 80f9d60 User stack: 134 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 134 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 134 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 134 __ZN9DSCThread3RunEv + 39 (in DirectoryServiceCore) [0x167f83] 134 __ZN17CMigHandlerThread10ThreadMainEv + 162 (in DirectoryService) [0x23768] 129 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 5 _mach_msg_server_once + 416 (in libSystem.B.dylib) [0x9509ee23] 5 _DSlibinfoMIG_server + 109 (in DirectoryService) [0x99b83] 5 __XQuery + 343 (in DirectoryService) [0x99e26] 5 _libinfoDSmig_do_Query + 585 (in DirectoryService) [0x2f3ad] 5 __ZN12CCachePlugin20ProcessLookupRequestEiPcii + 638 (in DirectoryService) [0x952fa] 5 __ZN12CCachePlugin13DSgetnameinfoEP7kvbuf_ti + 2142 (in DirectoryService) [0x8dfa0] 5 _idna_dns_lookup + 572 (in DirectoryService) [0xcf5f4] 5 _dns_lookup_soa_min + 215 (in libresolv.9.dylib) [0x9026e32b] 5 __sdns_search + 832 (in libresolv.9.dylib) [0x90269d56] 5 __pdns_query + 223 (in libresolv.9.dylib) [0x90269a03] 5 _res_nquery_soa_min + 356 (in libresolv.9.dylib) [0x90280785] 5 _res_9_nsend_2 + 65 (in libresolv.9.dylib) [0x902840a3] 5 _dns_res_send + 4332 (in libresolv.9.dylib) [0x90283de7] 5 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Thread id: 7322d60 User stack: 18 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 18 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 18 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 18 __ZN9DSCThread3RunEv + 39 (in DirectoryServiceCore) [0x167f83] 18 __ZN14CHandlerThread10ThreadMainEv + 87 (in DirectoryService) [0x7285] 18 __ZN9CMsgQueue13WaitOnMessageEm + 157 (in DirectoryService) [0x279bb] 18 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 8065048 User stack: 69 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 69 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 69 __ZN9DSLThread11_RunWrapperEPv + 84 (in DirectoryServiceCore) [0x16818e] 69 _syscall + 5 (in libSystem.B.dylib) [0x950841d5] Process: Dock [129] Path: /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock ADDRESS BINARY 00001000 /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock 22f80000 /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera Thread id: 6f2da78 User stack: 287 ??? [0x525e] 287 ??? [0x96b73] 287 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213 (in Foundation) [0x9438c135] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 286 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _CFRunLoopRunSpecific + 3896 (in CoreFoundation) [0x9388e908] 1 ___CFMachPortPerform + 117 (in CoreFoundation) [0x9386a635] 1 ??? [0x4d4a7] 1 ??? [0x49386] 1 _CGSPostBroadcastNotification + 79 (in CoreGraphics) [0x90ef0f10] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cbf3c8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x13204] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6f2c790 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 80f7000 User stack: 8 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 8 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 3 ??? [0x5331b] 3 _CGSReenableUpdate +

Re: SDLMAME and X-Arcade = crash Marc Mame #46030 11/03/08 02:29 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Part 2/2 [code] Process: WindowServer [65] Path: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer ADDRESS BINARY 00001000 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer 0001b000 /System/Library/Extensions/GeForceGA.plugin/Contents/MacOS/GeForceGA 21a00000 /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine 21bb1000 /System/Library/Extensions/GeForceFXGLDriver.bundle/Contents/MacOS/GeForceFXGLDriver 22800000 /System/Library/Extensions/GeForce8xxxGLDriver.bundle/Contents/MacOS/GeForce8xxxGLDriver 2457a000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib Thread id: 6950000 User stack: 287 start + 54 (in WindowServer) [0x1fbe] 287 _main + 24 (in WindowServer) [0x1ff4] 287 _CGXGetRootAdminCredentials + 0 (in CoreGraphics) [0x90f0e4f9] 287 _CGXServerLoop + 161 (in CoreGraphics) [0x90f7f4a6] 281 _CGXRunOneServicesPass + 377 (in CoreGraphics) [0x90f744bf] 238 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 38 _mach_msg_overwrite_trap + 10 (in libSystem.B.dylib) [0x950414b2] 5 _CGXRunOneServerPass + 556 (in CoreGraphics) [0x90f77ea0] 5 _CGXPostPortData + 158 (in CoreGraphics) [0x90f780aa] 4 _connectionHandler + 329 (in CoreGraphics) [0x90f8e4ab] 4 _CGXServices_server + 119 (in CoreGraphics) [0x90f8e789] 2 __XFlushRegionInline + 201 (in CoreGraphics) [0x90f90870] 2 __CGXFlushRegionInline + 234 (in CoreGraphics) [0x90f9098b] 2 _CGXFlushWindow + 39 (in CoreGraphics) [0x90f90a20] 2 _CGXFlushWindowList + 772 (in CoreGraphics) [0x90f90d27] 1 _CGXUpdateDisplay + 6494 (in CoreGraphics) [0x90f6caf1] 1 _CGXReleaseDisplayDeviceSurface + 247 (in CoreGraphics) [0x90f89a3b] 1 _CGXGLAccelFinish + 183 (in CoreGraphics) [0x90f8ab17] 1 _gldFinish + 1477 (in GeForceFXGLDriver) [0x21bd1925] 1 _gldGetString + 12741 (in GeForceFXGLDriver) [0x21bd0d75] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _CGXUpdateDisplay + 406 (in CoreGraphics) [0x90f6b329] 1 __CGXGetUpdateDisplayRegion + 782 (in CoreGraphics) [0x90f74e40] 1 _CGXCoreImageFilterGeometry + 161 (in CoreGraphics) [0x90fc4dad] 1 _cgxcoreimage_filter_geometry + 360 (in libCGXCoreImage.A.dylib) [0x2457c6e1] 1 _prepare_image + 644 (in libCGXCoreImage.A.dylib) [0x2457b3c6] 1 -[CIFilter valueForKey:] + 56 (in QuartzCore) [0x91e5d530] 1 -[NSObject(NSKeyValueCoding) valueForKey:] + 135 (in Foundation) [0x9437adc7] 1 -[CIMixOver outputImage] + 555 (in QuartzCore) [0x91f32b54] 1 -[CIFilter apply:] + 107 (in QuartzCore) [0x91e6432d] 1 -[CIKernel apply:to:options:] + 284 (in QuartzCore) [0x91e64451] 1 -[CIKernel apply:to:params:] + 1340 (in QuartzCore) [0x91e64a3c] 1 _class_respondsToSelector + 91 (in libobjc.A.dylib) [0x94f5e4de] 1 __cache_addForwardEntry + 74 (in libobjc.A.dylib) [0x94f5f603] 1 __class_isInitialized + 18 (in libobjc.A.dylib) [0x94f68495] 1 __XReenableUpdateForConnections + 184 (in CoreGraphics) [0x90f97c81] 1 __CGXReenableUpdateForConnections + 197 (in CoreGraphics) [0x90f97d82] 1 _CGXReenableUpdateForConnections + 176 (in CoreGraphics) [0x90f97e92] 1 _CGXUpdateDisplay + 406 (in CoreGraphics) [0x90f6b329] 1 __CGXGetUpdateDisplayRegion + 782 (in CoreGraphics) [0x90f74e40] 1 _CGXCoreImageFilterGeometry + 161 (in CoreGraphics) [0x90fc4dad] 1 _cgxcoreimage_filter_geometry + 360 (in libCGXCoreImage.A.dylib) [0x2457c6e1] 1 _prepare_image + 147 (in libCGXCoreImage.A.dylib) [0x2457b1d5] 1 -[CIFilter valueForKey:] + 56 (in QuartzCore) [0x91e5d530] 1 -[CIConcreteSampler release] + 1 (in QuartzCore) [0x91e969cf] 1 __XTerminateWindowList + 184 (in CoreGraphics) [0x90fa49ad] 1 __CGXTerminateWindowList + 270 (in CoreGraphics) [0x90fa4af7] 1 __CGXReleaseWindow + 846 (in CoreGraphics) [0x90f7df39] 1 _CGXBackingStoreRelease + 42 (in CoreGraphics) [0x90fa12ef] 1 _CGXBackingStoreTextureRelease + 29 (in CoreGraphics) [0x90f6eb66] 1 _CGXGLDestroyTexture + 125 (in CoreGraphics) [0x90fa14e2] 1 _glDeleteTextures_Exec + 406 (in GLEngine) [0x21a230e6] 1 _gleDeleteHashNamesAndObjects + 275 (in GLEngine) [0x21a233e3] 1 _gleFreeTextureObject + 38 (in GLEngine) [0x21a22b26] 1 _gleDeletePluginTexture + 81 (in GLEngine) [0x21a22c91] 1 _gldDeleteTexture + 30 (in GeForce8xxxGLDriver) [0x22809a5e] 1 _gldReclaimTexture + 485 (in GeForce8xxxGLDriver) [0x22809a35] 1 _IOConnectCallMethod + 300 (in IOKit) [0x91ca9d56] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _connectionHandler + 778 (in CoreGraphics) [0x90f8e66c] 1 _pushOutMessage + 9 (in CoreGraphics) [0x90f8b37a] 6 _CGXRunOneServicesPass + 139 (in CoreGraphics) [0x90f743d1] 6 __CGXRunTimerPass + 407 (in CoreGraphics) [0x90f63084] 5 _CGXUpdateDisplay + 6362 (in CoreGraphics) [0x90f6ca6d] 5 _CGLayerComposite + 335 (in CoreGraphics) [0x90f86350] 5 _CGGLAccelComposite + 102 (in CoreGraphics) [0x90f86baf] 2 _CGXGLAccelCompositeLayers + 1290 (in CoreGraphics) [0x90f8779a] 2 _cgxcoreimage_render_image + 355 (in libCGXCoreImage.A.dylib) [0x2457d341] 2 -[CIContextImpl render:] + 264 (in QuartzCore) [0x91ebff46] 2 -[CIOpenGLContextImpl renderWithBounds:matrix:function:info:] + 209 (in QuartzCore) [0x91ec001f] 2 _renderImage + 109 (in QuartzCore) [0x91f76da2] 2 _fe_image_render + 155 (in QuartzCore) [0x91ec1999] 2 _fe_image_render_ + 213 (in QuartzCore) [0x91e68acc] 2 _fe_tree_render_image + 923 (in QuartzCore) [0x91e6924b] 2 _fe_tree_render_tree + 196 (in QuartzCore) [0x91e7a37b] 2 _fe_tree_render_ + 1704 (in QuartzCore) [0x91e7ada5] 2 _fe_tree_render_apply + 827 (in QuartzCore) [0x91e7b6a5] 1 _fe_tree_create_texture + 1191 (in QuartzCore) [0x91e7bf51] 1 _fe_texture_new + 463 (in QuartzCore) [0x91e7d154] 1 _texture_retain + 674 (in QuartzCore) [0x91e7d58d] 1 _fe_tree_render_texture + 60 (in QuartzCore) [0x91eaf563] 1 _fe_tree_render_ + 3114 (in QuartzCore) [0x91e7b327] 1 _fe_context_collect_ + 103 (in QuartzCore) [0x91e96106] 1 _fe_context_update_buffers + 153 (in QuartzCore) [0x91e966a6] 1 _fe_release + 414 (in QuartzCore) [0x91e6427e] 1 _accel_buffer_last_unref + 56 (in QuartzCore) [0x91eb9b10] 1 _fe_release + 414 (in QuartzCore) [0x91e6427e] 1 _accel_buffer_finalize + 113 (in QuartzCore) [0x91ec8ba6] 1 _cglsDestroyPBuffer + 52 (in CoreGraphics) [0x90fc5ea0] 1 _IOServiceClose + 32 (in IOKit) [0x91caaa13] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _fe_tree_create_texture + 1447 (in QuartzCore) [0x91e7c051] 1 _fe_texture_copy + 413 (in QuartzCore) [0x91f2fee5] 1 _fe_gl_begin + 67 (in QuartzCore) [0x91eb895f] 1 _fe_gl_buffer_update + 142 (in QuartzCore) [0x91eb8a0e] 1 _fe_accel_buffer_attach + 768 (in QuartzCore) [0x91eb8d3c] 1 _glClear_Exec + 382 (in GLEngine) [0x21a24b6e] 1 _gldUpdateDispatch + 339 (in GeForce8xxxGLDriver) [0x2281e4d3] 1 _gldObjectUnpurgeable + 17410 (in GeForce8xxxGLDriver) [0x2281abc2] 1 _gldObjectUnpurgeable + 13585 (in GeForce8xxxGLDriver) [0x22819cd1] 1 _gldObjectUnpurgeable + 9158 (in GeForce8xxxGLDriver) [0x22818b86] 1 _IOConnectCallMethod + 300 (in IOKit) [0x91ca9d56] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 2 _CGXGLAccelCompositeLayers + 1467 (in CoreGraphics) [0x90f8784b] 2 _CGXGLAccelCompositeLayer_ + 7026 (in CoreGraphics) [0x90f8941b] 2 _glBegin_Exec + 296 (in GLEngine) [0x21a203d8] 1 _gldUpdateDispatch + 339 (in GeForce8xxxGLDriver) [0x2281e4d3] 1 _gldObjectUnpurgeable + 17435 (in GeForce8xxxGLDriver) [0x2281abdb] 1 _gldObjectUnpurgeable + 14188 (in GeForce8xxxGLDriver) [0x22819f2c] 1 _gldObjectUnpurgeable + 9158 (in GeForce8xxxGLDriver) [0x22818b86] 1 _IOConnectCallMethod + 300 (in IOKit) [0x91ca9d56] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _gldGetTextureLevel + 730211 (in GeForce8xxxGLDriver) [0x228dc553] 1 _CGXGLAccelCompositeLayer_ + 157 (in CoreGraphics) [0x90f87946] 1 _CGXUpdateDisplay + 2878 (in CoreGraphics) [0x90f6bcd1] 1 _CGXAcquireDisplayDeviceSurface + 3214 (in CoreGraphics) [0x90f80456] 1 _CGXGLAccelAccess + 168 (in CoreGraphics) [0x90f82435] 1 _cglsAttachDrawable + 178 (in CoreGraphics) [0x90f826e6] 1 _gliAttachDrawableWithOptions + 196 (in GLEngine) [0x21a106e4] 1 _gldAttachDrawable + 318 (in GeForce8xxxGLDriver) [0x22806f0e] 1 _IOConnectCallMethod + 300 (in IOKit) [0x91ca9d56] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 29 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 24 _mach_msg_overwrite_trap + 4783 [0x127216] 23 _ipc_mqueue_receive + 738 [0x120e9e] 23 _thread_block + 33 [0x136ac0] 23 _thread_block_reason + 135 [0x136a1c] 22 _thread_setrun + 3173 [0x135f10] 22 _machine_idle + 278 [0x1a2aab] 1 _thread_setrun + 1124 [0x13570f] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] 5 _mach_msg_overwrite_trap + 752 [0x126257] 3 _ipc_kobject_server + 247 [0x12d17e] 1 _iokit_server_routine + 3800 [0x1899e6] 1 _is_io_connect_map_memory + 84 [0x43e150] 1 _is_io_connect_map_memory_into_task + 87 [0x43e039] 1 __ZN12IOUserClient17mapClientMemory64EmP4taskmy + 72 [0x4397e0] 1 com.apple.GeForce (5.3.0) + 115251 [0x1031233] 1 _memcpy + 22 [0x198016] 1 _IOMapPages + 2392 [0x188185] 1 _is_io_service_close + 72 [0x43b058] 1 com.apple.GeForce (5.3.0) + 152681 [0x103a469] 1 com.apple.GeForce (5.3.0) + 484028 [0x108b2bc] 1 com.apple.GeForce (5.3.0) + 168415 [0x103e1df] 1 com.apple.GeForce (5.3.0) + 302328 [0x105ecf8] 1 com.apple.NVDAResman (5.3.0) + 30728 [0x628808] 1 com.apple.NVDAResman (5.3.0) + 81840 [0x634fb0] 1 com.apple.NVDAResman (5.3.0) + 132726 [0x641676] 1 com.apple.NVDAResman (5.3.0) + 90716 [0x63725c] 1 com.apple.NVDAResman (5.3.0) + 1411639 [0x779a37] 1 com.apple.NVDAResman (5.3.0) + 1410443 [0x77958b] 1 com.apple.NVDAResman (5.3.0) + 48814 [0x62ceae] 1 _iokit_server_routine + 20111 [0x18d99d] 1 _is_io_connect_method + 468 [0x43b3c8] 1 __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 747 [0x43d7c5] 1 _shim_io_connect_method_scalarI_scalarO + 477 [0x43b95f] 1 com.apple.GeForce (5.3.0) + 124434 [0x1033612] 1 com.apple.GeForce (5.3.0) + 185935 [0x104264f] 1 com.apple.GeForce (5.3.0) + 335582 [0x1066ede] 1 com.apple.GeForce (5.3.0) + 335111 [0x1066d07] 1 com.apple.NVDAResman (5.3.0) + 32492 [0x628eec] 1 com.apple.NVDAResman (5.3.0) + 82980 [0x635424] 1 com.apple.NVDAResman (5.3.0) + 134967 [0x641f37] 1 com.apple.NVDAResman (5.3.0) + 389441 [0x680141] 1 com.apple.nvidia.nv50hal (5.3.0) + 275123 [0xe5d2b3] 1 com.apple.nvidia.nv50hal (5.3.0) + 262553 [0xe5a199] 1 com.apple.nvidia.nv50hal (5.3.0) + 57682 [0xe28152] 1 com.apple.nvidia.nv50hal (5.3.0) + 38596 [0xe236c4] 1 com.apple.nvidia.nv50hal (5.3.0) + 37258 [0xe2318a] 1 com.apple.NVDAResman (5.3.0) + 352517 [0x677105] 1 com.apple.NVDAResman (5.3.0) + 1022383 [0x71a9af] 1 com.apple.NVDAResman (5.3.0) + 331589 [0x671f45] 1 com.apple.NVDAResman (5.3.0) + 331189 [0x671db5] 1 _ipc_kobject_server + 450 [0x12d249] 1 _mutex_lock + 68 [0x19aa14] 1 _ipc_kobject_server + 111 [0x12d0f6] 1 _ipc_kmsg_alloc + 168 [0x11d99f] 1 _kalloc_canblock + 16 [0x12f9b1] 5 _PE_incoming_interrupt + 131 [0x447f78] 5 _lapic_interrupt + 300 [0x1af933] 5 _sync_iss_to_iks + 114 [0x1a7fa8] 1 _thread_exception_return + 0 [0x19eca0] Thread id: 6cc1d60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___tickleThread + 41 (in IOKit) [0x91cebfe1] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc15d0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _eventThread + 499 (in CoreGraphics) [0x90f61e79] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 5 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 5 _mach_msg_overwrite_trap + 4783 [0x127216] 5 _ipc_mqueue_receive + 738 [0x120e9e] 5 _thread_block + 33 [0x136ac0] 5 _thread_block_reason + 135 [0x136a1c] 5 _thread_setrun + 3173 [0x135f10] 5 _machine_idle + 278 [0x1a2aab] Thread id: 6f307d8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _glvmDoWork + 162 (in libGLProgrammability.dylib) [0x93b67b32] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6f30048 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _layer_blit_async_thread + 95 (in CoreGraphics) [0x911fe392] 287 _layer_blit_thread + 229 (in CoreGraphics) [0x911fde6d] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6f2f128 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _layer_blit_async_thread + 95 (in CoreGraphics) [0x911fe392] 287 _layer_blit_thread + 229 (in CoreGraphics) [0x911fde6d] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6f2ed60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _layer_blit_async_thread + 95 (in CoreGraphics) [0x911fe392] 287 _layer_blit_thread + 229 (in CoreGraphics) [0x911fde6d] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Process: autofsd [38] Path: /usr/libexec/autofsd ADDRESS BINARY 00001000 /usr/libexec/autofsd Thread id: 67c6998 User stack: 287 ??? [0x1752] 287 ??? [0x1d8b] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: configd [35] Path: /usr/sbin/configd ADDRESS BINARY 00001000 /usr/sbin/configd 0003e000 /System/Library/SystemConfiguration/PrinterNotifications.bundle/Contents/MacOS/PrinterNotifications 00043000 /System/Library/SystemConfiguration/PowerManagement.bundle/Contents/MacOS/PowerManagement 00053000 /System/Library/SystemConfiguration/DynamicPowerStep.bundle/Contents/MacOS/DynamicPowerStep 00058000 /System/Library/SystemConfiguration/Bluetooth.bundle/Contents/MacOS/Bluetooth 0005e000 /System/Library/SystemConfiguration/BatteryUpdater.bundle/Contents/MacOS/BatteryUpdater 00063000 /System/Library/SystemConfiguration/Apple80211Monitor.bundle/Contents/MacOS/Apple80211Monitor 0007b000 /System/Library/SystemConfiguration/EAPOLController.bundle/EAPOLController 00084000 /System/Library/SystemConfiguration/IP6Configuration.bundle/Contents/MacOS/IP6Configuration 00096000 /System/Library/SystemConfiguration/IPConfiguration.bundle/Contents/MacOS/IPConfiguration 000c2000 /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 00200000 /System/Library/SystemConfiguration/PPPController.bundle/Contents/MacOS/PPPController Thread id: 67c74f0 User stack: 287 start + 54 (in configd) [0x220e] 287 _main + 2394 (in configd) [0x2c3f] 287 _server_loop + 70 (in configd) [0x39a6] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 601a208 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _plugin_exec + 1562 (in configd) [0x4c5b] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 69534f0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Process: coreaudiod [126] Path: /usr/sbin/coreaudiod ADDRESS BINARY 00001000 /usr/sbin/coreaudiod 00030000 /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugIn.bundle/Contents/MacOS/AudioIPCPlugIn 00039000 /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn 00200000 /Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder 70000000 /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio Thread id: 6cc2c80 User stack: 287 ??? [0x1e22] 287 ??? [0xaecb] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc02e8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 __ZN9CAPThread5EntryEPS_ + 96 (in CoreAudio) [0x907a3300] 287 __ZN10HALRunLoop9OwnThreadEPv + 160 (in CoreAudio) [0x907a3464] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: coreservicesd [45] Path: /System/Library/CoreServices/coreservicesd ADDRESS BINARY 00001000 /System/Library/CoreServices/coreservicesd Thread id: 67c87d8 User stack: 287 ??? [0x1f6e] 287 __CoreServicesServerMain + 795 (in CarbonCore) [0x91506b43] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 1 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 1 _mach_msg_overwrite_trap + 4783 [0x127216] 1 _ipc_mqueue_receive + 738 [0x120e9e] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Thread id: 6950f20 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 676cb58 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _fmodWatchConsumer + 407 (in CarbonCore) [0x9150c967] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6a1b790 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___read + 10 (in libSystem.B.dylib) [0x950651ba] Kernel stack: 287 _unix_syscall + 572 [0x3ddd6e] 287 _read_nocancel + 150 [0x38be6f] 287 _nosys + 593 [0x38bc2f] 287 _release_pathbuff + 3077 [0x1ff5f8] 287 _tsleep + 105 [0x380aa0] 287 _uiomove + 1030 [0x3807b8] 287 _thread_block + 33 [0x136ac0] 287 _thread_continue + 1181 [0x136853] Process: cupsd [251] Path: /usr/sbin/cupsd ADDRESS BINARY 0b557000 /usr/sbin/cupsd 0b5ba000 /usr/lib/libpam.1.dylib Thread id: 810d5d0 User stack: 287 start + 54 (in cupsd) [0xb5579b6] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 80fb410 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _cupsdUpdateSystemMonitor + 2174 (in cupsd) [0xb59b1f1] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: diskarbitrationd [32] Path: /usr/sbin/diskarbitrationd ADDRESS BINARY 00001000 /usr/sbin/diskarbitrationd Thread id: 67c8048 User stack: 287 ??? [0x1a5a] 287 ??? [0x8a7a] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: distnoted [44] Path: /usr/sbin/distnoted ADDRESS BINARY 00001000 /usr/sbin/distnoted Thread id: 67c52e8 User stack: 287 ??? [0x1ef6] 287 ??? [0x1f95] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: dynamic_pager [29] Path: /sbin/dynamic_pager ADDRESS BINARY Thread id: 67c8ba0 User stack: 287 ??? [0x178a] 287 ??? [0x2a11] 287 ??? [0x2224] 287 ??? [0x1efd] 287 ??? [0x950414a6] Process: fseventsd [27] Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Support/fseventsd ADDRESS BINARY 00001000 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Support/fseventsd Thread id: 676c3c8 User stack: 287 ??? [0x25a2] 287 ??? [0x2fcc] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 67c56b0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0xbbd9] 287 ??? [0xb92d] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 67c43c8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x44d6] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 67c4000 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___read + 10 (in libSystem.B.dylib) [0x950651ba] Kernel stack: 287 _unix_syscall + 572 [0x3ddd6e] 287 _read_nocancel + 150 [0x38be6f] 287 _nosys + 593 [0x38bc2f] 287 _release_pathbuff + 3077 [0x1ff5f8] 287 _tsleep + 105 [0x380aa0] 287 _uiomove + 1030 [0x3807b8] 287 _thread_block + 33 [0x136ac0] 287 _thread_continue + 1181 [0x136853] Thread id: 6954ba0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x9834] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6a1e8b8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 6cc3410 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x9834] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6cc06b0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x9834] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6f2fc80 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x9834] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 7324ba0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x9834] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Process: hidd [26] Path: /usr/libexec/hidd ADDRESS BINARY 00001000 /usr/libexec/hidd Thread id: 676c790 User stack: 287 ??? [0x1f76] 287 ??? [0x1fef] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 676ed60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___tickleThread + 41 (in IOKit) [0x91cebfe1] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: iTunesHelper [141] Path: /Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/MacOS/iTunesHelper ADDRESS BINARY 00001000 /Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/MacOS/iTunesHelper 00300000 /System/Library/PrivateFrameworks/MobileDevice.framework/MobileDevice Thread id: 7324410 User stack: 287 ??? [0x1c99] 287 ??? [0x1d72] 287 ??? [0x2a2e] 287 _RunApplicationEventLoop + 207 (in HIToolbox) [0x96c204ab] 287 __AcquireNextEvent + 58 (in HIToolbox) [0x96c21d4e] 287 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 287 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 744b3c8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Process: kextd [10] Path: /usr/libexec/kextd ADDRESS BINARY 00001000 /usr/libexec/kextd Thread id: 61a48b8 User stack: 287 ??? [0x1b4e] 287 ??? [0x356b] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 60d2128 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0x3c11] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 287 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 287 _mach_msg_overwrite_trap + 752 [0x126257] 287 _ipc_kobject_server + 247 [0x12d17e] 287 _host_priv_server_routine + 3711 [0x147c60] 287 _kmod_control + 243 [0x18f626] 287 _thread_sleep_mutex + 71 [0x136fb3] 287 _thread_continue + 1181 [0x136853] Process: launchd [1] Path: /sbin/launchd ADDRESS BINARY 00001000 /sbin/launchd Thread id: 60d15d0 User stack: 287 start + 54 (in launchd) [0x1fd2] 287 _main + 960 (in launchd) [0x2a17] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 212 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 212 _mach_msg_overwrite_trap + 3771 [0x126e22] 212 _ipc_mqueue_receive + 750 [0x120eaa] 212 _thread_block + 33 [0x136ac0] 212 _thread_continue + 1181 [0x136853] Thread id: 61a4c80 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Thread id: 61a2e40 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: launchd [114] Path: /sbin/launchd ADDRESS BINARY 00001000 /sbin/launchd Thread id: 67c4f20 User stack: 287 start + 54 (in launchd) [0x1fd2] 287 _main + 960 (in launchd) [0x2a17] 286 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 1 _launchd_runtime + 572 (in launchd) [0x14fa5] 1 _mig_deallocate + 43 (in libSystem.B.dylib) [0x950885ba] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Kernel stack: 287 _dtrace_get_cpu_int_stack_top + 543 [0x1974c2] 286 _mach_msg_overwrite_trap + 3771 [0x126e22] 286 _ipc_mqueue_receive + 750 [0x120eaa] 286 _thread_block + 33 [0x136ac0] 286 _thread_continue + 1181 [0x136853] 1 _mach_msg_overwrite_trap + 752 [0x126257] 1 _ipc_kobject_server + 247 [0x12d17e] 1 _vm_map_server_routine + 940 [0x159209] 1 _vm_deallocate + 96 [0x182541] 1 _vm_map_remove + 50 [0x16a3d8] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] Thread id: 6953c80 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 286 ___select + 10 (in libSystem.B.dylib) [0x950915e2] 1 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 1 _kqueue_demand_loop + 192 (in launchd) [0x13a89] 1 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1ce40 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: loginwindow [23] Path: /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow ADDRESS BINARY 00001000 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow 00075000 /System/Library/PrivateFrameworks/Admin.framework/Versions/A/Admin 000bf000 /System/Library/PrivateFrameworks/URLMount.framework/Versions/A/URLMount 000ec000 /System/Library/LoginPlugins/FSDisconnect.loginPlugin/Contents/MacOS/FSDisconnect 0015e000 /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages 002bc000 /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit 00303000 /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording 00437000 /usr/lib/libcurl.4.dylib 0046c000 /System/Library/LoginPlugins/DisplayServices.loginPlugin/Contents/MacOS/DisplayServices 0048b000 /System/Library/LoginPlugins/BezelServices.loginPlugin/Contents/MacOS/BezelServices 004b9000 /System/Library/PrivateFrameworks/MachineSettings.framework/Versions/A/MachineSettings 004f3000 /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugIn.bundle/Contents/MacOS/AudioIPCPlugIn 00740000 /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn 24add000 /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera Thread id: 676d2e8 User stack: 287 ??? [0x5816] 287 ??? [0x1b838] 287 -[NSApplication run] + 795 (in AppKit) [0x922a6cdb] 287 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x922adca0] 287 __DPSNextEvent + 657 (in AppKit) [0x922ae3ed] 287 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x96bc310d] 287 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x96bc3299] 287 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x96bc3480] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6f2f4f0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_overwrite_trap + 10 (in libSystem.B.dylib) [0x950414b2] Thread id: 744ec80 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 __ZN9CAPThread5EntryEPS_ + 96 (in CoreAudio) [0x907a3300] 287 __ZN10HALRunLoop9OwnThreadEPv + 160 (in CoreAudio) [0x907a3464] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: mDNSResponder [22] Path: /usr/sbin/mDNSResponder ADDRESS BINARY 00001000 /usr/sbin/mDNSResponder Thread id: 676d6b0 User stack: 287 start + 41 (in mDNSResponder) [0x2229] 287 __start + 210 (in mDNSResponder) [0x22fc] 287 _main + 2606 (in mDNSResponder) [0x368cb] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1f7d8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Process: mds [21] Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds ADDRESS BINARY 00001000 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds 000d9000 /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel 0014d000 /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex 0372b000 /usr/lib/liblangid.dylib 03c1a000 /usr/lib/libmecab.1.0.0.dylib Thread id: 61a1000 User stack: 287 ??? [0x5c56] 287 ??? [0xe9c3] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 69525d0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0xd91d] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6951a78 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0xd940] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6950b58 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0xd963] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6950790 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0xd986] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 69503c8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0xd9a9] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1d998 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 254 ??? [0xa6f7] 254 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] 33 ??? [0xa65a] 33 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 6a1d5d0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___read + 10 (in libSystem.B.dylib) [0x950651ba] Kernel stack: 287 _unix_syscall + 572 [0x3ddd6e] 287 _read_nocancel + 150 [0x38be6f] 287 _nosys + 593 [0x38bc2f] 287 _release_pathbuff + 3077 [0x1ff5f8] 287 _tsleep + 105 [0x380aa0] 287 _uiomove + 1030 [0x3807b8] 287 _thread_block + 33 [0x136ac0] 287 _thread_continue + 1181 [0x136853] Thread id: 67c4790 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 69516b0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0x87d1f] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1d208 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0x54c9d] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1b3c8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0x54c9d] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6a1b000 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0x54c9d] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc37d8 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc2128 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 -[NSThread main] + 45 (in Foundation) [0x94357bad] 287 ??? [0x58e18] 287 ??? [0x45423] 287 ??? [0x5904a] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 7322998 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _setattr_runLoop + 68 (in SpotlightIndex) [0x17a9e4] 287 _runLoop + 77 (in SpotlightIndex) [0x17a8f8] 286 _si_scheduler_run_waiting_timeout + 163 (in SpotlightIndex) [0x18ed10] 286 _semaphore_timedwait_signal_trap + 10 (in libSystem.B.dylib) [0x95041506] 1 _si_scheduler_run_waiting_timeout + 581 (in SpotlightIndex) [0x18eeb2] 1 _si_scheduler_once + 419 (in SpotlightIndex) [0x18eb27] 1 _si_scheduler_once + 419 (in SpotlightIndex) [0x18eb27] 1 _si_work_queue_process + 643 (in SpotlightIndex) [0x18e839] 1 _si_delete_attributes + 130 (in SpotlightIndex) [0x17e3c5] 1 _db_get_obj_callback + 537 (in SpotlightIndex) [0x165f19] 1 _page_find_oid + 62 (in SpotlightIndex) [0x15c11e] 1 _page_fetch + 303 (in SpotlightIndex) [0x15a72f] 1 _db_flush_cache + 306 (in SpotlightIndex) [0x159c12] 1 _munmap$UNIX2003 + 10 (in libSystem.B.dylib) [0x9504ad3e] Kernel stack: 1 _unix_syscall + 572 [0x3ddd6e] 1 _munmap + 154 [0x374fe8] 1 _mach_vm_deallocate + 132 [0x1824c7] 1 _vm_map_remove + 50 [0x16a3d8] 1 _lck_rw_lock_exclusive + 560 [0x19e6ce] 1 _ml_set_interrupts_enabled + 47 [0x1a2389] Process: mdworker [176] Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker ADDRESS BINARY 00001000 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker 0004f000 /System/Library/Spotlight/Application.mdimporter/Contents/MacOS/Application 00055000 /System/Library/Spotlight/Bookmarks.mdimporter/Contents/MacOS/Bookmarks 0005b000 /System/Library/Spotlight/RichText.mdimporter/Contents/MacOS/RichText Thread id: 7324048 User stack: 287 ??? [0x21f2] 287 ??? [0x8740] 287 ??? [0xb95d] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 60d1d60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 285 ??? [0xa20c] 285 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] 2 ??? [0x92db] 2 ??? [0x5a0b] 1 _GetMetadataForFile + 1978 (in RichText) [0x602aa] 1 -[NSAttributedString(NSAttributedStringKitAdditions) initWithURL:options:documentAttributes:error:] + 232 (in AppKit) [0x92590aca] 1 __NSReadAttributedStringFromURLOrData + 5793 (in AppKit) [0x9241f65b] 1 ___read + 10 (in libSystem.B.dylib) [0x950651ba] 1 _GetMetadataForFile + 955 (in RichText) [0x5feab] 1 ___read + 10 (in libSystem.B.dylib) [0x950651ba] Kernel stack: 2 _unix_syscall + 572 [0x3ddd6e] 2 _read_nocancel + 150 [0x38be6f] 2 _nosys + 593 [0x38bc2f] 2 _vn_rdwr + 353 [0x1ebd74] 2 _VNOP_READ + 168 [0x1f638c] 2 _hfs_vnop_read + 308 [0x3280af] 2 _cluster_read + 61 [0x1d172b] 1 _cluster_read_ext + 1904 [0x1d1069] 1 _msleep + 157 [0x3809f0] 1 _uiomove + 653 [0x38063f] 1 _lck_mtx_sleep + 87 [0x130a21] 1 _thread_block + 33 [0x136ac0] 1 _thread_continue + 1181 [0x136853] 1 _cluster_read_ext + 2011 [0x1d10d4] 1 _cluster_pageout + 2945 [0x1cf60a] 1 _msleep + 157 [0x3809f0] 1 _uiomove + 653 [0x38063f] 1 _lck_mtx_sleep + 87 [0x130a21] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Thread id: 6a1e4f0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Thread id: 6cbff20 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Process: mdworker [265] Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker ADDRESS BINARY 00001000 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker Thread id: 6a1ca78 User stack: 287 ??? [0x21f2] 287 ??? [0x8740] 287 ??? [0xb95d] 287 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x9388ecf8] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 81b1d60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0xa20c] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 6cc1998 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ___NSThread__main__ + 308 (in Foundation) [0x94357754] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Process: notifyd [11] Path: /usr/sbin/notifyd ADDRESS BINARY Thread id: 6018b58 User stack: 287 ??? [0x1fc6] 287 ??? [0x95071f66] Thread id: 61a5ba0 User stack: 287 ??? [0x950725b2] 287 ??? [0x950726f5] 287 ??? [0x950414a6] Process: ntpd [14] Path: /usr/sbin/ntpd ADDRESS BINARY 00001000 /usr/sbin/ntpd Thread id: 61a1790 User stack: 287 ??? [0x203a] 287 ___sigsuspend + 10 (in libSystem.B.dylib) [0x9509d34a] Process: pboard [127] Path: /usr/sbin/pboard ADDRESS BINARY 00001000 /usr/sbin/pboard Thread id: 6a1bb58 User stack: 287 ??? [0x1f26] 287 ___sigsuspend + 10 (in libSystem.B.dylib) [0x9509d34a] Process: securityd [19] Path: /usr/sbin/securityd ADDRESS BINARY 00001000 /usr/sbin/securityd 000bc000 /System/Library/Frameworks/PCSC.framework/Versions/A/PCSC Thread id: 67707d8 User stack: 287 ??? [0x1211a] 287 ??? [0x295e] 287 ??? [0x3f32] 287 _mach_msg_overwrite_trap + 10 (in libSystem.B.dylib) [0x950414b2] Thread id: 809ed60 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 ??? [0xa9ca] 287 ??? [0xaa1c] 287 _mach_msg_overwrite_trap + 10 (in libSystem.B.dylib) [0x950414b2] Process: socketfilterfw [39] Path: /usr/libexec/ApplicationFirewall/socketfilterfw ADDRESS BINARY 00001000 /usr/libexec/ApplicationFirewall/socketfilterfw Thread id: 67c65d0 User stack: 287 ??? [0x21f6] 287 ??? [0x8366] 287 ??? [0x5a56] 287 ??? [0x7359] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 676de40 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Thread id: 6952208 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___kevent + 10 (in libSystem.B.dylib) [0x95071f66] Process: spindump [266] Path: /usr/sbin/spindump ADDRESS BINARY Thread id: 80f9208 User stack: 287 ??? [0x950841d5] Kernel stack: 287 _unix_syscall + 572 [0x3ddd6e] 287 _stack_snapshot2 + 133 [0x352c3a] Thread id: 6cc3ba0 User stack: 287 ??? [0x950725b2] 287 ??? [0x950726f5] 287 ??? [0x950414a6] Process: syslogd [12] Path: /usr/sbin/syslogd ADDRESS BINARY 00001000 /usr/sbin/syslogd Thread id: 676f128 User stack: 285 ___select + 10 (in libSystem.B.dylib) [0x950915e2] 2 start + 54 (in syslogd) [0x1982] 2 _main + 4483 (in syslogd) [0x899f] 1 _aslevent_handleevent + 203 (in syslogd) [0x56e4] 1 _aslevent_match + 63 (in syslogd) [0x4744] 1 _asl_action_sendmsg + 24 (in syslogd) [0x1dd4] 1 _aslevent_handleevent + 150 (in syslogd) [0x56af] 1 _whatsmyhostname + 265 (in syslogd) [0x4890] 1 _asl_parse_time + 485 (in libSystem.B.dylib) [0x950a4df7] 1 _sstep + 56 (in libSystem.B.dylib) [0x950a6788] Kernel stack: 2 _PE_incoming_interrupt + 131 [0x447f78] 2 _lapic_interrupt + 300 [0x1af933] 2 _sync_iss_to_iks + 114 [0x1a7fa8] Thread id: 676e998 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 676e5d0 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _db_worker + 144 (in syslogd) [0x65d3] 287 _db_dequeue + 56 (in syslogd) [0x64e3] 287 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] Thread id: 676e208 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 __pthread_start + 321 (in libSystem.B.dylib) [0x950726f5] 287 _launchd_drain + 73 (in syslogd) [0x5617] 287 __vprocmgr_log_drain + 75 (in libSystem.B.dylib) [0x951641be] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Process: update [15] Path: /usr/sbin/update ADDRESS BINARY 00001000 /usr/sbin/update Thread id: 6770410 User stack: 283 ??? [0x1f3a] 283 ??? [0x1fd9] 283 ___semwait_signal + 10 (in libSystem.B.dylib) [0x9504868e] 4 _sync + 10 (in libSystem.B.dylib) [0x9509ae12] Kernel stack: 4 _unix_syscall + 572 [0x3ddd6e] 4 _sync + 34 [0x1e0340] 4 _vfs_iterate + 204 [0x1db0e3] 4 _mount_dropcrossref + 240 [0x1e030b] 4 _VFS_SYNC + 111 [0x1f68f4] 4 _hfs_mark_volume_inconsistent + 9644 [0x333ac7] 4 _journal_flush + 608 [0x1face5] 3 _journal_modify_block_start + 4417 [0x1fa190] 3 _journal_modify_block_start + 4118 [0x1fa065] 3 _journal_uses_fua + 105 [0x1f7825] 3 _VNOP_IOCTL + 209 [0x1f619c] 3 _spec_ioctl + 176 [0x202e5a] 3 com.apple.iokit.IOStorageFamily (1.5.2) + 62229 [0xa88315] 3 com.apple.iokit.IOAHCIBlockStorage (1.1.1) + 24804 [0x10b70e4] 3 com.apple.iokit.IOAHCIBlockStorage (1.1.1) + 12738 [0x10b41c2] 3 _IORecursiveLockSleep + 67 [0x404e3b] 3 _lck_mtx_sleep + 87 [0x130a21] 3 _thread_block + 33 [0x136ac0] 3 _thread_continue + 1181 [0x136853] 1 _journal_modify_block_start + 6157 [0x1fa85c] 1 _journal_uses_fua + 105 [0x1f7825] 1 _VNOP_IOCTL + 209 [0x1f619c] 1 _spec_ioctl + 176 [0x202e5a] 1 com.apple.iokit.IOStorageFamily (1.5.2) + 62229 [0xa88315] 1 com.apple.iokit.IOAHCIBlockStorage (1.1.1) + 24804 [0x10b70e4] 1 com.apple.iokit.IOAHCIBlockStorage (1.1.1) + 12738 [0x10b41c2] 1 _IORecursiveLockSleep + 67 [0x404e3b] 1 _lck_mtx_sleep + 87 [0x130a21] 1 _thread_block + 33 [0x136ac0] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Process: usbmuxd [146] Path: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/Resources/usbmuxd ADDRESS BINARY 00001000 /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/Resources/usbmuxd Thread id: 744bf20 User stack: 287 ??? [0x2161] 287 ??? [0x2234] 287 ??? [0x2938] 287 _CFRunLoopRun + 84 (in CoreFoundation) [0x9388ed54] 287 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x950414a6] Thread id: 744b790 User stack: 287 _thread_start + 34 (in libSystem.B.dylib) [0x950725b2] 287 ___select + 10 (in libSystem.B.dylib) [0x950915e2] Process: kernel_task [0] Path: kernel_task ADDRESS BINARY Thread id: 519120 Thread id: 601cba0 Kernel stack: 2 _idle_thread + 23 [0x137352] 2 _machine_idle + 278 [0x1a2aab] Thread id: 601c7d8 Thread id: 601c410 Thread id: 601c048 Thread id: 601bc80 Thread id: 601b8b8 Thread id: 601b128 Thread id: 6018000 Thread id: 60d37d8 Kernel stack: 287 _buf_list_unlock + 95 [0x1c7ec9] 287 _msleep + 157 [0x3809f0] 287 _uiomove + 653 [0x38063f] 287 _lck_mtx_sleep + 87 [0x130a21] 287 _thread_block + 33 [0x136ac0] 287 _thread_continue + 1181 [0x136853] Thread id: 60d3048 Kernel stack: 1 __ZN10IOWorkLoop10threadMainEv + 191 [0x41f809] 1 _thread_block_parameter + 32 [0x136a9d] 1 _thread_block_reason + 135 [0x136a1c] 1 _thread_setrun + 3173 [0x135f10] 1 _machine_idle + 278 [0x1a2aab] Thread id: 60d3ba0 Kernel stack: 1 _idle_thread + 23 [0x137352] 1 _machine_idle + 278 [0x1a2aab] Thread id: 6019a78 Thread id: 6019e40 Thread id: 60d3410 Thread id: 60cf3c8 Thread id: 60cfb58 Thread id:

Re: SDLMAME and X-Arcade = crash Marc Mame #46031 11/03/08 02:38 AM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Is your SDL 1.2.13? 1.2.12 can crash like that on OS X.

Re: SDLMAME and X-Arcade = crash R. Belmont #46033 11/03/08 02:44 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Yep 1.2.13

Re: SDLMAME and X-Arcade = crash Marc Mame #46034 11/03/08 02:46 AM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Yeah, looking at the backtrace more it appears that the Mac version of SDL is simply not compatible with the X-Arcade for some reason.

Re: SDLMAME and X-Arcade = crash

Marc Mame #46035 11/03/08 02:51 AM

Joined: Sep 2000

Posts: 286

Paris, France

Marc Mame

Senior Member

Marc Mame

Senior Member

Joined: Sep 2000

Posts: 286

Paris, France

Ok, new compile is done.
First, ran a gdb mame done this :
(without X-Arcade)

Code

Last login: Mon Nov  3 03:37:53 on ttys000
bgn92-2-82-66-95-27:~ MarcV$ cd /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2 
bgn92-2-82-66-95-27:sdlmame0128u2 MarcV$ % gdb mame
-bash: fg: %: no such job
bgn92-2-82-66-95-27:sdlmame0128u2 MarcV$ gdb mame
GNU gdb 6.3.50-20050815 (Apple version gdb-768) (Tue Oct  2 04:07:49 UTC 2007)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin"...
warning: Unable to read symbols for "@executable_path/../Frameworks/SDL.framework/Versions/A/SDL" (file not found).
Reading symbols for shared libraries ........... done

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(atarifb.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(atarifb.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(atarifb.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(avalnche.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(bzone.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(jaguar.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(copsnrob.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(copsnrob.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(runaway.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(tunhunt.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(videopin.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atari.a(videopin.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/atlus.a(blmbycar.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/capcom.a(higemaru.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/cinemat.a(cinemat.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/cinemat.a(cinemat.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/comad.a(funybubl.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/dataeast.a(brkthru.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/dataeast.a(dietgo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/dataeast.a(madmotor.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/exidy.a(carpolo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/exidy.a(circus.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/exidy.a(circus.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/gametron.a(gotya.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/gametron.a(gatron.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/irem.a(redalert.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/jaleco.a(ginganin.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/jaleco.a(tetrisp2.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/kaneko.a(suprnova.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/konami.a(88games.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/konami.a(pandoras.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/meadows.a(lazercmd.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/meadows.a(meadows.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/meadows.a(meadows.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(8080bw.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(8080bw.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(mw8080bw.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(mw8080bw.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(mw8080bw.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midw8080.a(sspeedr.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midway.a(astrocde.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midway.a(midtunit.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/midway.a(midzeus.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/namco.a(namcos21.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/namco.a(tceptor.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/namco.a(warpwarp.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/namco.a(warpwarp.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/namco.a(psx.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/neogeo.a(neogeo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/nichibut.a(nbmj8688.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/nichibut.a(nbmj9195.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/nichibut.a(niyanpai.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/pacman.a(pacman.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/playmark.a(sderby.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sega.a(model2.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sega.a(segas32.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sega.a(stactics.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sega.a(turbo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sega.a(turbo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/seibu.a(legionna.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/seta.a(seta.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sigma.a(spiders.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/sun.a(kangaroo.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(arkanoid.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(arkanoid.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(darius.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(qix.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(qix.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(qix.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(taito_l.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/taito.a(tnzs.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/tatsumi.a(tx1.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/tatsumi.a(tx1.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/tatsumi.a(tx1.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/technos.a(matmania.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/technos.a(wwfwfest.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/tehkan.a(wc90b.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/univers.a(cheekyms.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/upl.a(nova2001.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/zaccaria.a(zac2650.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(ampoker2.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(cave.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(funworld.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(lucky74.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(snookr10.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/mame/misc.a(usgames.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/libemu.a(generic.o)" more recent than executable timestamp

warning: .o file "/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/obj/sdl/mame/libemu.a(generic.o)" more recent than executable timestamp

(gdb)

Re: SDLMAME and X-Arcade = crash R. Belmont #46036 11/03/08 03:00 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by R. Belmont Yeah, looking at the backtrace more it appears that the Mac version of SDL is simply not compatible with the X-Arcade for some reason. Looks like bad news to my ears... What can we do about it ?

Re: SDLMAME and X-Arcade = crash

Marc Mame #46037 11/03/08 03:12 AM

Joined: Sep 2000

Posts: 286

Paris, France

Marc Mame

Senior Member

Marc Mame

Senior Member

Joined: Sep 2000

Posts: 286

Paris, France

Continuing with new build :

run pacman (without X-Arcade)

Code

(gdb) run pacman
Starting program: /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/mame pacman
Reading symbols for shared libraries .++++++++++............................................................................ done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries .. done
Loading BDF font... (256 characters loaded)
Loading BDF font... (512 characters loaded)
Loading BDF font... (768 characters loaded)
Loading BDF font... (1024 characters loaded)
Loading BDF font... (1280 characters loaded)
Loading BDF font... (1536 characters loaded)
Generating cached BDF font...
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries .. done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
pacman.6e NOT FOUND
pacman.6f NOT FOUND
pacman.6h NOT FOUND
pacman.6j NOT FOUND
pacman.5e NOT FOUND
pacman.5f NOT FOUND
82s123.7f NOT FOUND
82s126.4a NOT FOUND
82s126.1m NOT FOUND
82s126.3m NOT FOUND
ERROR: required files are missing, the game cannot be run.
Ignoring MAME exception: pacman.6e NOT FOUND
pacman.6f NOT FOUND
pacman.6h NOT FOUND
pacman.6j NOT FOUND
pacman.5e NOT FOUND
pacman.5f NOT FOUND
82s123.7f NOT FOUND
82s126.4a NOT FOUND
82s126.1m NOT FOUND
82s126.3m NOT FOUND
ERROR: required files are missing, the game cannot be run.

Program exited with code 02.

Next

run pacman (with X-Arcade attached)

Code

(gdb) run pacman
Starting program: /Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/mame pacman
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done

Almost half an hour and still hanging there. One processor core @ 100% for the MAME task.

Open files and ports for MAME :

Code

/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2
/Volumes/MacOS9/MacMAME/SDLMame/sdlmame0128u2/mame
/Library/Frameworks/SDL.framework/Versions/A/SDL
/System/Library/Fonts/LucidaGrande.dfont
/private/var/folders/dS/dSAe3XpnHGeQpYqd4sSDO++++TI/-Caches-/com.apple.ATS/annex_aux
/usr/share/icu/icudt36l.dat
/System/Library/Fonts/Helvetica.dfont
/private/var/folders/dS/dSAe3XpnHGeQpYqd4sSDO++++TI/-Caches-/com.apple.IntlDataCache.le.sbdl
/Library/Caches/com.apple.LaunchServices-023501.csstore
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/Extras2.rsrc
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/HIToolbox.rsrc
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/English.lproj/Localized.rsrc
/System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib
/usr/lib/dyld
/private/var/db/dyld/dyld_shared_cache_i386
/dev/ttys000
/dev/ttys000
/dev/ttys000
->0x634edd0
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/Extras2.rsrc
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/HIToolbox.rsrc
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/English.lproj/Localized.rsrc

Re: SDLMAME and X-Arcade = crash Marc Mame #46040 11/03/08 03:23 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I cant quit MAME so I'm afraid I won't be able to do a backtrace. Is there another way to force quit an app ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46041 11/03/08 04:41 AM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Ok. When it locks up and is taking 100%, click in the terminal window where GDB is running and press control-Z. That should halt MAME and get you to where you can do a backtrace.

Re: SDLMAME and X-Arcade = crash R. Belmont #46060 11/03/08 02:18 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Control Z seems to have no effect. It just display : ^Z on terminal screen what am I doing wrong ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46061 11/03/08 02:19 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Alright. Try Control-C.

Re: SDLMAME and X-Arcade = crash R. Belmont #46067 11/03/08 03:27 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	No change It just display : ^C on terminal screen

Re: SDLMAME and X-Arcade = crash Marc Mame #46069 11/03/08 03:30 PM
Joined: Oct 2002 Posts: 1,017 M MooglyGuy Senior Member
MooglyGuy Senior Member M Joined: Oct 2002 Posts: 1,017	This is probably not going to work, but if you have an AZERTY keyboard, try Ctrl+W, maybe, since W on an AZERTY keyboard is where Z is on a QWERTY keyboard?

Re: SDLMAME and X-Arcade = crash MooglyGuy #46072 11/03/08 03:49 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I do have an AZERTY layout but when I press the "w" or "z" key, it's a "w" or "z" that show on screen. I've tried anyway, even Control W does nothing but ^w on terminal screen. Seems that the task can't be halted.

Re: SDLMAME and X-Arcade = crash Marc Mame #46073 11/03/08 03:51 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Richard, are you saying it's the SDL framework that could be the cause of the crash ? Not SDLMAME ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46074 11/03/08 03:58 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Without some way to interrupt the process (Vas Crabb might have an idea, he knows OS X better than I do) it's difficult to know for sure.

Re: SDLMAME and X-Arcade = crash R. Belmont #46129 11/04/08 10:25 AM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	OK, so interrupting the process with GDB doesn't do anything, which means it isn't responding to asynchronous signals. Force quit doesn't do anything, either, so it's locked up bad. From my (relatively limited) experience writing USB drivers for OSX, this looks a lot like a deadlock or livelock inside the kernel (OSX uses one kernel thread for each USB root hub, so you can screw up pretty badly and still maintain a partially usable system). A few tests may reveal more: When it's in this state, does unplugging the device cause SDLMAME to crash, or does it have no effect? If you connect the device via an external USB hub, when you get SDLMAME to lock up, do other USB devices connected to the same hub stop working? Does the device work with other applications that access the HID key elements, as opposed to the HID boot interface? (Most of the time, OSX is only reading codes from the boot interface - it's mainly games that watch the key elements directly. I don't know how SDL does it. You can try using something like HIDDeviceTest from DDHidLib to test it.) It looks a lot like the device has a dodgy HID protocol implementation to me.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46133 11/04/08 12:11 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Vas Crabb OK, so interrupting the process with GDB doesn't do anything, which means it isn't responding to asynchronous signals. Force quit doesn't do anything, either, so it's locked up bad. Yeah, force quit doesn't do anything at all but the MacPro still allow to be restarted clean without a forced shutdown. Quote When it's in this state, does unplugging the device cause SDLMAME to crash, or does it have no effect? No effect. Quote If you connect the device via an external USB hub, when you get SDLMAME to lock up, do other USB devices connected to the same hub stop working? I don't have any USB hub but I guess I could try to hook it up on the back of the keyboard... I'll try that. Quote Does the device work with other applications that access the HID key elements, as opposed to the HID boot interface? No Idea. What I do know it's working fine with MAME OS X and respond correctly in TextEdit as the device act as a real Keyboard, not as a joystick element. Quote You can try using something like HIDDeviceTest from DDHidLib to test it.) I've no clue how to use it...

Re: SDLMAME and X-Arcade = crash Marc Mame #46134 11/04/08 12:22 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Something new ! Saving my system information lock up in the middle of reading history the same way : one processor core @100%. The locked up process is called ioreg. Maybe there's a way to verbose the process and backtrace it with the terminal ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46135 11/04/08 12:43 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	If it's what I think it is, and ioreg locking up makes it look more like my hunch is correct, you'll need a two-machine kernel debugging setup with debug versions of the IOKit USB modules to get a backtrace - not for the faint of heart! Seriously, I don't think you'll get anywhere without a firmware update for the device.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46137 11/04/08 01:13 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	FWIW here's the Sys info report : Quote Bus USB : Emplacement du contr�leur de l�h�te : USB int�gr� Gestionnaire du contr�leur de l�h�te : AppleUSBUHCI Identifiant du p�riph�rique PCI : 0x2688 Identifiant de r�vision du PCI : 0x0009 Identifiant du fournisseur du PCI : 0x8086 Num�ro de bus : 0x1d X-Arcade : Version : 1.00 Alimentation du BUS (mA) : 500 Vitesse : Jusqu�� 1,5 Mb/s Fabricant : XGaming Identifiant du produit : 0x0101 Identifiant du fournisseur : 0xaa55

Re: SDLMAME and X-Arcade = crash Vas Crabb #46139 11/04/08 01:33 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Vas Crabb If it's what I think it is, and ioreg locking up makes it look more like my hunch is correct, you'll need a two-machine kernel debugging setup with debug versions of the IOKit USB modules to get a backtrace - not for the faint of heart! Seriously, I don't think you'll get anywhere without a firmware update for the device. So you think it's more like the firmware device rather than a bug in the OS ? I'm not even sure this device can support a firmware upgrade. Do you ? You should know that I've trashed AppleHIDMouseAgent.plugin from sys/lib/UserEventPlugin since it was a supposedly known source of pb with X-Arcade. ( Mac running slow as written on X-Arcade support site ) if it has anything to do with it... Should I try to put it back ? I've contacted X-Gaming support and a case has been opened. We'll see where it goes... Anyway, thanks for your time and support Vas and all.

Re: SDLMAME and X-Arcade = crash

Marc Mame #46141 11/04/08 02:28 PM

Joined: Sep 2000

Posts: 286

Paris, France

Marc Mame

Senior Member

Marc Mame

Senior Member

Joined: Sep 2000

Posts: 286

Paris, France

Not sure if that would be of any help but here's it goes :

USB Bus Probe results :

Code

Full Speed device @ 1 (0x1D000000): .............................................   Hub device: "UHCI Root Hub Simulation"

Low Speed device @ 2 (0x1D100000): .............................................   Composite device: "X-Arcade"
    Device Descriptor   
        Descriptor Version Number:   0x0110
        Device Class:   0   (Composite)
        Device Subclass:   0
        Device Protocol:   0
        Device MaxPacketSize:   8
        Device VendorID/ProductID:   0xAA55/0x0101   (unknown vendor)
        Device Version Number:   0x0100
        Number of Configurations:   1
        Manufacturer String:   1 "XGaming"
        Product String:   2 "X-Arcade"
        Serial Number String:   0 (none)
    Configuration Descriptor: .......................................   "HID Keyboard"
        Length (and contents):   59
            Raw Descriptor (hex)    0000: 09 02 3B 00 02 01 04 A0  32 09 04 00 00 01 03 01  
            Raw Descriptor (hex)    0010: 01 05 09 21 10 01 00 01  22 3F 00 07 05 81 03 08  
            Raw Descriptor (hex)    0020: 00 0A 09 04 01 00 01 03  00 00 00 09 21 10 01 00  
            Raw Descriptor (hex)    0030: 01 22 66 00 07 05 82 03  04 00 FF 
        Number of Interfaces:   2
        Configuration Value:   1
        Attributes:   0xA0 (bus-powered, remote wakeup)
        MaxPower:   100 ma
        Interface #0 - HID/Boot Interface   
            Alternate Setting   0
            Number of Endpoints   1
            Interface Class:   3   (HID)
            Interface Subclass;   1   (Boot Interface)
            Interface Protocol:   1
            HID Descriptor   
                Descriptor Version Number:   0x0110
                Country Code:   0
                Descriptor Count:   1
                Descriptor 1   
                    Type:   0x22  (Report Descriptor)
                    Length (and contents):   63
                        Raw Descriptor (hex)    0000: 05 01 09 06 A1 01 05 07  19 E0 29 E7 15 00 25 01  
                        Raw Descriptor (hex)    0010: 75 01 95 08 81 02 95 01  75 08 81 01 95 05 75 01  
                        Raw Descriptor (hex)    0020: 05 08 19 01 29 05 91 02  95 01 75 03 91 01 95 06  
                        Raw Descriptor (hex)    0030: 75 08 15 00 25 65 05 07  19 00 29 65 81 00 C0 
                    Parsed Report Descriptor:   
                          Usage Page    (Generic Desktop) 
                          Usage (Keyboard)    
                              Collection (Application)    
                                Usage Page    (Keyboard/Keypad) 
                                Usage Minimum...........    (224)  
                                Usage Maximum...........    (231)  
                                Logical Minimum.........    (0)  
                                Logical Maximum.........    (1)  
                                Report Size.............    (1)  
                                Report Count............    (8)  
                                Input...................   (Data, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Bitfield) 
                                Report Count............    (1)  
                                Report Size.............    (8)  
                                Input...................   (Constant, Array, Absolute) 
                                Report Count............    (5)  
                                Report Size.............    (1)  
                                Usage Page    (LED) 
                                Usage Minimum...........    (1)  
                                Usage Maximum...........    (5)  
                                Output..................   (Data, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Report Count............    (1)  
                                Report Size.............    (3)  
                                Output..................   (Constant, Array, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Report Count............    (6)  
                                Report Size.............    (8)  
                                Logical Minimum.........    (0)  
                                Logical Maximum.........    (101)  
                                Usage Page    (Keyboard/Keypad) 
                                Usage Minimum...........    (0)  
                                Usage Maximum...........    (101)  
                                Input...................   (Data, Array, Absolute) 
                              End Collection     
            Endpoint 0x81 - Interrupt Input   
                Address:   0x81  (IN)
                Attributes:   0x03  (Interrupt no synchronization data endpoint)
                Max Packet Size:   8
                Polling Interval:   10 ms
        Interface #1 - HID   
            Alternate Setting   0
            Number of Endpoints   1
            Interface Class:   3   (HID)
            Interface Subclass;   0
            Interface Protocol:   0
            HID Descriptor   
                Descriptor Version Number:   0x0110
                Country Code:   0
                Descriptor Count:   1
                Descriptor 1   
                    Type:   0x22  (Report Descriptor)
                    Length (and contents):   102
                        Raw Descriptor (hex)    0000: 05 01 09 80 A1 01 85 02  75 01 95 03 15 00 25 01  
                        Raw Descriptor (hex)    0010: 19 81 29 83 81 06 75 05  95 01 81 01 C0 05 0C 09  
                        Raw Descriptor (hex)    0020: 01 A1 01 85 03 95 01 75  10 19 00 2A FF 7F 81 00  
                        Raw Descriptor (hex)    0030: C0 06 7F FF 09 03 A1 01  85 04 95 01 75 10 19 00  
                        Raw Descriptor (hex)    0040: 2A FF 7F 81 00 75 02 25  02 09 90 B1 02 75 06 B1  
                        Raw Descriptor (hex)    0050: 01 75 01 25 01 05 08 09  2A 91 02 09 4B 91 02 75  
                        Raw Descriptor (hex)    0060: 06 95 01 91 01 C0 
                    Parsed Report Descriptor:   
                          Usage Page    (Generic Desktop) 
                          Usage (System Control)    
                              Collection (Application)    
                                ReportID................    (2)  
                                Report Size.............    (1)  
                                Report Count............    (3)  
                                Logical Minimum.........    (0)  
                                Logical Maximum.........    (1)  
                                Usage Minimum...........    (129)  
                                Usage Maximum...........    (131)  
                                Input...................   (Data, Variable, Relative, No Wrap, Linear, Preferred State, No Null Position, Bitfield) 
                                Report Size.............    (5)  
                                Report Count............    (1)  
                                Input...................   (Constant, Array, Absolute) 
                              End Collection     
                          Usage Page    (Consumer) 
                          Usage 1 (0x1)    
                              Collection (Application)    
                                ReportID................    (3)  
                                Report Count............    (1)  
                                Report Size.............    (16)  
                                Usage Minimum...........    (0)  
                                Usage Maximum...........    (32767)  
                                Input...................   (Data, Array, Absolute) 
                              End Collection     
                          Usage Page    (65407) 
                          Usage 3 (0x3)    
                              Collection (Application)    
                                ReportID................    (4)  
                                Report Count............    (1)  
                                Report Size.............    (16)  
                                Usage Minimum...........    (0)  
                                Usage Maximum...........    (32767)  
                                Input...................   (Data, Array, Absolute) 
                                Report Size.............    (2)  
                                Logical Maximum.........    (2)  
                                Usage 144 (0x90)    
                                Feature.................   (Data, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Report Size.............    (6)  
                                Feature.................   (Constant, Array, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Report Size.............    (1)  
                                Logical Maximum.........    (1)  
                                Usage Page    (LED) 
                                Usage 42 (0x2a)    
                                Output..................   (Data, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Usage 75 (0x4b)    
                                Output..................   (Data, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                                Report Size.............    (6)  
                                Report Count............    (1)  
                                Output..................   (Constant, Array, Absolute, No Wrap, Linear, Preferred State, No Null Position, Nonvolatile, Bitfield) 
                              End Collection     
            Endpoint 0x82 - Interrupt Input   
                Address:   0x82  (IN)
                Attributes:   0x03  (Interrupt no synchronization data endpoint)
                Max Packet Size:   4
                Polling Interval:   255 ms

Full Speed device @ 1 (0x3D000000): .............................................   Hub device: "UHCI Root Hub Simulation"
Low Speed device @ 2 (0x3D100000): .............................................   Composite device: "Microsoft Wireless Optical Mouse\256 1.0A"
Full Speed device @ 3 (0x3D200000): .............................................   Hub device: "Hub in Apple Extended USB Keyboard"
Full Speed device @ 4 (0x3D230000): .............................................   Composite device: "Apple Extended USB Keyboard"
Full Speed device @ 1 (0x5D000000): .............................................   Hub device: "UHCI Root Hub Simulation"
Full Speed device @ 1 (0x7D000000): .............................................   Hub device: "UHCI Root Hub Simulation"
High Speed device @ 1 (0xFD000000): .............................................   Hub device: "EHCI Root Hub Simulation"

Re: SDLMAME and X-Arcade = crash Marc Mame #46152 11/04/08 08:22 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	Originally Posted by Marc Mame You should know that I've trashed AppleHIDMouseAgent.plugin from sys/lib/UserEventPlugin since it was a supposedly known source of pb with X-Arcade. ( Mac running slow as written on X-Arcade support site ) if it has anything to do with it... Should I try to put it back ? Yeah, put it back. The fact that they want you to remove it should be a sign that not all is right with the device to begin with. I don't think it's a driver issue. Apple's HID driver is pretty solid, and works with a huge variety of devices.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46153 11/04/08 09:21 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Just put it back and rebooted. As soon as I plug the X-Arcade, UserEventAgent hog 100% of a core. I do remember the first time I plugged the X-Arcade, the finder pop up a dialog box to set up the new hardware but I skipped. What should I do to get that set up to show again ? (if any use)

Re: SDLMAME and X-Arcade = crash Marc Mame #46161 11/05/08 07:43 AM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	That dialog box helps you set whether the keyboard is ANSI, ISO or JIS layout, and whether it has Windows or Mac modifier arrangement. It isn't really relevant for a joystick.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46165 11/05/08 11:06 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Vas Crabb It isn't really relevant for a joystick. Yeah but as I understand it, from the computer point of view, the X-Arcade is a keyboard, not a joystick (and it does act as a keyboard). Quote On a PC or Mac, the buttons and joysticks are assigned to specific keyboard and mouse keys, think of the X-Arcade as an integrated keyboard and mouse. When you press a button on the X-Arcade your computer thinks you are pressing a key on your keyboard or mouse (even modifier keys like left or right CTRL, ALT or Shift). For example, if you open a word editor, you will notice that the buttons and joysticks type. Last edited by Marc Mame; 11/05/08 11:20 AM.

Re: SDLMAME and X-Arcade = crash Marc Mame #46168 11/05/08 11:50 AM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	Yes, I know, but would the differences between ANSI, ISO and JIS layout make a difference for the X-arcade?

Re: SDLMAME and X-Arcade = crash Vas Crabb #46169 11/05/08 12:49 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Guess not. But since I don't have a clue, It's just a supposition. Assuming IOreg is the culprit, why MAMEOS X (and other games or word editor) doesn't call for it but SDLMAME does ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46170 11/05/08 01:21 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	We can't really answer that without knowing what invalid Microsoft-ism they ingrained into the Xarcade's firmware.

Re: SDLMAME and X-Arcade = crash R. Belmont #46182 11/05/08 08:33 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	IOReg isn't the culprit. Some issue with the device's HID protocol implementation is causing the kernel driver to deadlock. It only seems to happen when software tries to access the more low-level features of the device. The standard keyboard driver only uses the HID boot interface for reading keystrokes - it never looks at raw key elements. The standard mouse driver doesn't do anything funky, either. Note that even the Apple mouse plugin causes problems. I've never seen that with any other HID device.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46192 11/06/08 10:23 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Vas Crabb IOReg isn't the culprit. Some issue with the device's HID protocol implementation is causing the kernel driver to deadlock. It only seems to happen when software tries to access the more low-level features of the device. The standard keyboard driver only uses the HID boot interface for reading keystrokes - it never looks at raw key elements. The standard mouse driver doesn't do anything funky, either. Note that even the Apple mouse plugin causes problems. I've never seen that with any other HID device. Thanks for the explanation Vas. I must be doomed... X-Arcade support seems to not be able to reproduce that bug but they ran their tests against SDLMAME 0.122u2. Is it possible that something has changed in the SDLMAME code source between 0.122u2 and 0.128u2 regarding that specific pb ?? Originally Posted by Vas Crabb You can try using something like HIDDeviceTest from DDHidLib to test it.) Can you please explain how to run this test ? Or is it a waste of time ?

Re: SDLMAME and X-Arcade = crash Marc Mame #46254 11/09/08 07:31 PM
Joined: Jul 2008 Posts: 5 T TDK Member
TDK Member T Joined: Jul 2008 Posts: 5	You have to build the project file(s) into a working binary with XCode (which is a free download via Apple Developer Connection). Last edited by TDK; 11/09/08 07:37 PM.

Re: SDLMAME and X-Arcade = crash TDK #46405 11/21/08 11:30 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Some news... I've decided to start from scratch to push away an possible driver conflict. So, here what I've done : 1) Took a new blank formated hard drive 2) Installed a fresh Mac OS X 10.5.5 with all update 3) Installed SDL Framework (1.2.13) from http://www.libsdl.org/download-1.2.php 4) Downloaded SDLMAME 0.122u2 from http://www.mametesters.net/sdlmame/ 5) Deleted AppleHIDMouseAgent.plugin from system/Library/UserEventPlugin 6) Rebooted 7) Connected X-Arcade Tankstick's USB cord 8) Open Terminal 9) Run Mame Result : Colored wheel of death... as always !! X-Gaming is sending me a replacement USB adapter to see if that may have been what's causing the problem. We'll see...

Re: SDLMAME and X-Arcade = crash Marc Mame #46406 11/21/08 11:32 AM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	Have you tried it with a Belkin or Aten USB-PS/2 adaptor? You could get more success that way.

Re: SDLMAME and X-Arcade = crash Vas Crabb #46407 11/21/08 01:24 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I'm not sure I can do that. The X-Arcade cable is just a serial cable (9 pins) that split in PS2/USB on the PC/Mac end The PCB is proprietary and inside the controller. Like this :

Re: SDLMAME and X-Arcade = crash Vas Crabb #46546 11/27/08 04:03 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Vas Crabb You can try using something like HIDDeviceTest from DDHidLib to test it. It looks a lot like the device has a dodgy HID protocol implementation to me. So, I've just tried Dave's Utilities. The HIDBrowser is just poping the colored wheel of death like SDLMAME do. The HIDDeviceTest is working and respond to keystroke. Oddly enough, the X-Arcade seems to send two caracters per keystroke : upper case and lower case. Not sure it has something to do with that mess....

Re: SDLMAME and X-Arcade = crash Marc Mame #46549 11/27/08 09:03 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	It's not sending two keystrokes. It's perfectly normal. So now if we can work out what the browser is doing that the device test isn't, we can give the guys a reproducible test case. Any ideas, Dave?

Re: SDLMAME and X-Arcade = crash Vas Crabb #47162 01/03/09 01:00 PM
Joined: Feb 2008 Posts: 6 T Triangel7D Member
Triangel7D Member T Joined: Feb 2008 Posts: 6	Marc Mame -- I recently switched to SDLMame since Mame OSX would not allow me to properly use my new LCD monitor stand that rotates 90 degrees. I finally had everything up and running yesterday, plugged in my X-Arcade and got the Beach Ball of Death. Luckily I found your thread! Thank you for all your hard work so far. Have you made any progress in the last month? Any response from XGaming? They were fairly responsive with my questions about the lack of NUM LOCK on my newer Macbook. My answers got added to the website immediately. But ultimately, isn't the issue with SDLMame (this issue doesn't exist with MacMAME or Mame OSX)? Do you know if they're working on it?

Re: SDLMAME and X-Arcade = crash Triangel7D #47164 01/03/09 03:04 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	No, the issue is that the Xarcade is just non-standard enough to cause some components of OS X to blow up. The problem is Apple's and X-Gaming's to solve unfortunately.

Re: SDLMAME and X-Arcade = crash Triangel7D #47213 01/05/09 06:14 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Triangel7D I finally had everything up and running yesterday, plugged in my X-Arcade and got the Beach Ball of Death. Did you trash the "AppleHIDMouseAgent.plugin" (from "sys/lib/UserEventPlugin") ? Quote Luckily I found your thread! Thank you for all your hard work so far. Have you made any progress in the last month? Not much. They send me a replacement USB breakout cable: it did not change a thing. Quote Any response from XGaming? Sure, they respond to each mail I've sent but to say that they cannot reproduce that problem... Quote They were fairly responsive with my questions about the lack of NUM LOCK on my newer Macbook. My answers got added to the website immediately. What kind of pb is related to the NUM Lock ? Quote Do you know if they're working on it? Can't say for sure. But the more we are with that same pb, the less they can ignore it !

Re: SDLMAME and X-Arcade = crash Marc Mame #47379 01/11/09 01:08 AM
Joined: Feb 2008 Posts: 6 T Triangel7D Member
Triangel7D Member T Joined: Feb 2008 Posts: 6	Originally Posted by Marc Mame Did you trash the "AppleHIDMouseAgent.plugin" (from "sys/lib/UserEventPlugin") ? Yes. I had that problem early on when I got the X-Arcade, but I think after a few system updates it came back, so I trashed it again. Beach ball. Quote Not much. They send me a replacement USB breakout cable: it did not change a thing. Do you have an older X-Arcade that needed a separate USB thingy or a newer one (like I have) that came with it? Quote Sure, they respond to each mail I've sent but to say that they cannot reproduce that problem... When I dealt with them with the num lock issue, I had the impression they were using old Macs (or old systems). Quote What kind of pb is related to the NUM Lock ? You know it's been so long, I can't remember what my problem was. It had something to do with something they said on the site about Mac users having to use the Num Lock key, but my newer MacBook did not have one (they got rid of it in 2007). Right after I brought it up to them, they updated the site. Quote Can't say for sure. But the more we are with that same pb, the less they can ignore it ! I'll definitely shoot them an email detailing my problem. Marc Mame, have you had any luck with SDLMAME .129? Since my last attempt, I no longer have room on my hard drive for the .129 roms (I keep the .124 roms on for MAME OSX). I actually prefer MAME OSX, since I've gotten pretty used to it over the last year. My only problem with it now is that it doesn't work full screen with games that turn the monitor 90 degrees and I can't use my nifty new monitor stand!

Re: SDLMAME and X-Arcade = crash Triangel7D #47421 01/12/09 06:00 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Triangel7D Yes. I had that problem early on when I got the X-Arcade, but I think after a few system updates it came back, so I trashed it again. Beach ball. Yep, has been updated with 10.5.6 so it needs to be removed again. Quote Do you have an older X-Arcade that needed a separate USB thingy or a newer one (like I have) that came with it? I've a brand new TankStick (2 players with trackball) The X-Arcade cable is just a serial cable (9 pins) that split in PS2/USB on the Mac end (see my earlier post for the image) Trackball has a separate USB cord. Quote When I dealt with them with the num lock issue, I had the impression they were using old Macs (or old systems). They tried on a MacPro as they said. Quote I'll definitely shoot them an email detailing my problem. Please keep me posted. Quote Marc Mame, have you had any luck with SDLMAME .129? Since my last attempt, I no longer have room on my hard drive for the .129 roms (I keep the .124 roms on for MAME OSX). No luck. I've tried every new version that came out without success. But you don't need any roms to test it since when it fails, it's way before you can load any rom.

Re: SDLMAME and X-Arcade = crash Triangel7D #47422 01/12/09 06:01 PM
Joined: Feb 2008 Posts: 6 T Triangel7D Member
Triangel7D Member T Joined: Feb 2008 Posts: 6	Update: I've opened up a case with X-Gaming. I'm relatively clueless as to how these things work, but using the PS/2 out on the X-Arcade and a PS/2 to USB adapter bypass the problem?

Re: SDLMAME and X-Arcade = crash Triangel7D #47440 01/13/09 10:03 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Triangel7D Update: I've opened up a case with X-Gaming. I guess you'll be talking to Lisa from their support. My real name is Marc Vielfaure if you want to refresh their memory... Quote I'm relatively clueless as to how these things work, but using the PS/2 out on the X-Arcade and a PS/2 to USB adapter bypass the problem? I'm not sure it would work at all on a mac with such adapter. I don't have one to test anyway. Last edited by Marc Mame; 01/13/09 10:04 AM.

Re: SDLMAME and X-Arcade = crash Marc Mame #49147 04/06/09 10:01 PM
Joined: Apr 2009 Posts: 5 skurk Member
skurk Member Joined: Apr 2009 Posts: 5	i just signed up to let you guys know that i have the exact same issue as the others in here. if i can help in any way, please let me know. i have performed all the same tests and diagnostics as described here with the exact same results...

Re: SDLMAME and X-Arcade = crash skurk #49152 04/07/09 10:10 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Welcome aboard Skurk ! You definitively should contact X-Gaming's support about this and let us know ! Last edited by Marc Mame; 04/07/09 10:11 AM.

Re: SDLMAME and X-Arcade = crash Marc Mame #49153 04/07/09 12:04 PM
Joined: Apr 2009 Posts: 5 skurk Member
skurk Member Joined: Apr 2009 Posts: 5	are we sure this is a problem with the X-Arcade and not the SDL framework?

Re: SDLMAME and X-Arcade = crash skurk #49154 04/07/09 12:22 PM
Joined: May 2008 Posts: 4,930 Likes: 24 Germany Q qmc2 Very Senior Member
qmc2 Very Senior Member Q Joined: May 2008 Posts: 4,930 Likes: 24 Germany	Judging from the other posts in this thread, I think the answer is "yes, we can" (be sure) ! When the X-Arcade sticks present themselves as keyboards (HID devices), how should SDL be causing the issue? As far as I understand what's been said here, it's the kernel driver that crashes, so it's Apple's / X-Arcade's job to fix it. Also, there's a post above mentioning another (non-SDL) application that also causes the crash... A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

Re: SDLMAME and X-Arcade = crash qmc2 #49155 04/07/09 01:03 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	Yes, it's an issue with the X-Arcade. Note that it isn't just SDL that causes the issue - running ioreg triggers it, and writing an application that probes all the HID values triggers it. They even tell you to remove AppleHIDMouseAgent.plugin as it can trigger the issue (doing so means you lose some Mighty Mouse features). If you need to remove an OS component that's part of a default install to use a device, that's a sure sign it has issues. (Now you could argue that the Apple HID driver shouldn't hang even if you connect a dodgy device, but the fact that it doesn't hang for any other known device on the market is evidence that it's pretty solid. I've worked on USB devices, and no buggy firmware I've put on a device has caused issues like this, either. I don't know what the X-Arcade does, but it must be pretty bad.)

Re: SDLMAME and X-Arcade = crash Vas Crabb #49158 04/07/09 03:46 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Yep... And above all, X-Gaming's support keep saying they can't reproduce that behavior... Yeah, right....

Re: SDLMAME and X-Arcade = crash Marc Mame #49181 04/08/09 09:31 PM
Joined: Apr 2009 Posts: 5 skurk Member
skurk Member Joined: Apr 2009 Posts: 5	Just curious: what mouse and keyboard are you using? They came back to me with a reply, and they blame OS X and drivers...

Re: SDLMAME and X-Arcade = crash skurk #49182 04/08/09 09:44 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by skurk Just curious: what mouse and keyboard are you using? Apple's stock. Quote They came back to me with a reply, and they blame OS X and drivers... Yeah, they already tried that with me, and others who dare to complain...

Re: SDLMAME and X-Arcade = crash Marc Mame #49183 04/08/09 09:52 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Someone so equipped should get a USB trace of the X-Arcade being buggy.

Re: SDLMAME and X-Arcade = crash R. Belmont #49184 04/08/09 09:58 PM
Joined: Apr 2009 Posts: 5 skurk Member
skurk Member Joined: Apr 2009 Posts: 5	i think that is beyond my capabilities, sadly.

Re: SDLMAME and X-Arcade = crash skurk #49185 04/08/09 10:26 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	All you need is a Windows XP box, USB Snoopy and some C++ skills (and an X-Arcade, which I lack).

Re: SDLMAME and X-Arcade = crash Vas Crabb #49206 04/09/09 07:14 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I do have all of that but lack the C++ skills... If you're willing to take me by the hand, I probably could do it ?

Re: SDLMAME and X-Arcade = crash Marc Mame #49304 04/13/09 09:58 AM
Joined: Apr 2009 Posts: 5 skurk Member
skurk Member Joined: Apr 2009 Posts: 5	Okay, this is starting to tick me off a little now... the ONLY emulator I have that works for me, is Mame OSX. When I start Snes9x with the X-Arcade plugged in, it crashes like SDLMame. Same thing with Genesis Plus. I too have now reinstalled Leopard since I was having additional USB errors, but this issue remains. Are you able to use any other emulators?

Re: SDLMAME and X-Arcade = crash skurk #49309 04/13/09 12:41 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	The X-Arcade has defective USB support - like many peripheral makers, they implemented the bare minimum to make Microsoft OSes work. Unlike most, they did it in a sufficiently slipshod way that it actually crashes Mac OS X instead of just being incompatible. It is not the fault of any individual emulator or a specific Leopard install. I strongly suggest trying to get a refund on the X-Arcade and buying something better behaved - a PS3 compatible fighting stick would probably work well.

Re: SDLMAME and X-Arcade = crash skurk #49311 04/13/09 01:00 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by skurk Okay, this is starting to tick me off a little now... the ONLY emulator I have that works for me, is Mame OSX. When I start Snes9x with the X-Arcade plugged in, it crashes like SDLMame. Same thing with Genesis Plus. I too have now reinstalled Leopard since I was having additional USB errors, but this issue remains. Are you able to use any other emulators? Unfortunatly, MAME OS X and SDLMAME are the only emulators I tried with the X-Arcade.

Re: SDLMAME and X-Arcade = crash R. Belmont #49312 04/13/09 01:13 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by R. Belmont The X-Arcade has defective USB support - like many peripheral makers, they implemented the bare minimum to make Microsoft OSes work. Unlike most, they did it in a sufficiently slipshod way that it actually crashes Mac OS X instead of just being incompatible. It is not the fault of any individual emulator or a specific Leopard install. I'm pretty sure they never developped the X-Arcade with OS X compatibility in mind. Once it was ready to ship for windows, they tried to find a way to sell it to Mac users without investing a dime in it. They should just do their job by either : - Warn their clients - Stop telling it's fully OS X compatible - Work out bugs Just my thoughts... Originally Posted by R. Belmont I strongly suggest trying to get a refund on the X-Arcade and buying something better behaved - a PS3 compatible fighting stick would probably work well. Unfortunately, I don't know any other real, heavy, rugged USB arcade sticks (2 players + track ball) that would be fully OS X compliant...

Re: SDLMAME and X-Arcade = crash Marc Mame #49313 04/13/09 01:17 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Well, when SlikStick was still in business those worked well. If you really must have an X-Arcade and need it to work on OS X you could always gut the existing encoder and wire up a USB iPac or something similar, although obviously "some assembly is required" for that

Re: SDLMAME and X-Arcade = crash R. Belmont #49316 04/13/09 03:47 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	And some not-so-cheap money too...

Re: SDLMAME and X-Arcade = crash Marc Mame #49378 04/16/09 10:35 AM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	I have the same problem with OS X 10.5.6 and X-Arcade Tankstick. I bought Tankstick with the intension to replace the joysticks with better ones. I got two Ultrasticks 360 from ultimarc.com. These are analog programmable joysticks that also support up to 8 buttons each. I replaced the original joysticks with these and wired the 8 player buttons to each of them. They work fine under OS X as they are recognized as HID joysticks. You have to change their ID first (on a PC running XP or in my case running an XP virtual machine under Parallels 4). The nice thing with these is that you can reprogram them as analog, 2-way, 4-way, 4-way diagonal, 8-away, or anything else you like (the programming software runs under XP but works fine with a virtual machine). The only drawback is that you lose the 1-2 player and the 2 side buttons with SDLmame and the Ultrasticks are expensive... Another solution is to replace the X-arcade controller with a U-HID (www.u-hid.com) which is also an expensive solution.

Re: SDLMAME and X-Arcade = crash Geoman #49380 04/16/09 01:26 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Given that probably less than a dozen games in MAME use more than 6 buttons you could also just lose 2 of the 8 to coin and start for each player.

Re: SDLMAME and X-Arcade = crash R. Belmont #49388 04/16/09 03:09 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	Originally Posted by R. Belmont Given that probably less than a dozen games in MAME use more than 6 buttons you could also just lose 2 of the 8 to coin and start for each player. With the latest firmware Ultrasticks use button 8 as a "shift" button: while holding button 8 down, pressing another button generates buttons 9-15 (instead of the normal 1-8). So you have another 7 buttons per Ultrastick to use for Coins, Player start, e.t.c.

Re: SDLMAME and X-Arcade = crash Geoman #49468 04/19/09 05:30 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	Someone reported that using the older USB PC/MAC ADAPTER solves the problem. I don't have one but maybe it is a convertor and not just an adapter.

Re: SDLMAME and X-Arcade = crash Geoman #49683 04/29/09 02:01 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	hi, i just found this thread. i bought a 1 player x-arcade (which was stated to be mac compatible) last year but haven't used it until now. reading x-arcade homepage i moved AppleHIDMouseAgent.plugin outta the way so the usb connection doesn't hog my cpu. of course this is a lame solution due a bad usb development from x-arcade. anywhow, i found that once connected the cpu stays quiet but whenever i launch any app, that app freezes, it doesn't force quits and i have to restart my macbook. so i guess it doesn't just crashes with sdlmame. so i found i have to first launch the game or app and then connect the x-arcade. the downside is that after exiting the app/game i have to disconnect the x-arcade again and so on. any new discoveries on a fix for this?

Re: SDLMAME and X-Arcade = crash straycat #49684 04/29/09 05:51 PM
Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA L Lord Nightmare Very Senior Member
Lord Nightmare Very Senior Member L Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA	The fix for this is known, but will probably never happen (unless someone dumps the old firmware and disassembles it; the x-arcade people have apparently shown exactly zero interest in fixing it themselves or helping it get fixed, as far as I'm aware; I could be wrong): The firmware for the x-arcade needs to be patched and reflashed to the unit, so it properly enumerates itself as a usb device, and behaves as it enumerated itself. Another fix would be to have apple fix their usb driver so it doesn't hang the whole system when badly-behaved devices like the x-arcade are connected. LN "When life gives you zombies... CHA-CHIK! ...you make zombie-ade!"

Re: SDLMAME and X-Arcade = crash Lord Nightmare #49685 04/29/09 06:06 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Yeah - even if you're going to enforce the standard (as opposed to just copying Microsoft's version of it like Linux and BSD do nowadays) a badly-behaved device should never be able to bring down the system.

Re: SDLMAME and X-Arcade = crash R. Belmont #49689 04/29/09 06:56 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	thanks for the heads-up, guys. i sent a mail to xgaming too but i believe neither them or apple is willing to take the plunge even if it's not apple's fault, anyway. xgaming didn't even bother to enable programming on os x. we have to use a ps/2 keyboard. on this thread, al3ph says "I just use my old xarcade usb adaptor with this, instead of the built in usb." and that it worked with him. i guess it's the universal serial bus (last one on the list). could they have fixed usb support with this hub and let it slip silently?

Re: SDLMAME and X-Arcade = crash straycat #49690 04/29/09 09:23 PM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	It doesn't bring down the entire system. It just locks up one kernel thread. You can save your work in other applications (provided your other input devices aren't connected to the same USB root hub) before restarting.

Re: SDLMAME and X-Arcade = crash Vas Crabb #49691 04/29/09 09:38 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Locking up a kernel thread in a microkernel system is still a pretty serious DoS.

Re: SDLMAME and X-Arcade = crash R. Belmont #49692 04/29/09 10:40 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	I know it's not an ideal solution, but what about writing a workaround in the SDL framework ?

Re: SDLMAME and X-Arcade = crash Marc Mame #49693 04/29/09 11:46 PM
Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA L Lord Nightmare Very Senior Member
Lord Nightmare Very Senior Member L Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA	Can't be done. The problem exists between the controller and the OS; SDL is above the OS and below MAME, it has nothing to do with the problem and can't help anything afaik. The two solutions were presented above: 1. fix the firmware 2. fix the OS LN "When life gives you zombies... CHA-CHIK! ...you make zombie-ade!"

Re: SDLMAME and X-Arcade = crash Lord Nightmare #49700 04/30/09 11:21 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Lord Nightmare Can't be done. The problem exists between the controller and the OS; SDL is above the OS and below MAME, it has nothing to do with the problem and can't help anything afaik. The two solutions were presented above: 1. fix the firmware 2. fix the OS How do you explain that MAME OS X can use the X-Arcade controller without crashing then ? If MAME OS X can do it, why SDLMAME couldn't ? Last edited by Marc Mame; 04/30/09 11:22 PM.

Re: SDLMAME and X-Arcade = crash Marc Mame #49701 04/30/09 11:31 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	I contacted the X-Arcade guys and asked them about their USB PC/Mac Adaptor. They told me that this is not just a simple adaptor but a convertor. So it may work because Tankstick only comes with an adaptor, but i don't have one to test. They told me that they will try their convertor and they will let me know if it actually works.

Re: SDLMAME and X-Arcade = crash Marc Mame #49705 05/01/09 06:36 AM
Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA L Lord Nightmare Very Senior Member
Lord Nightmare Very Senior Member L Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA	Originally Posted by Marc Mame How do you explain that MAME OS X can use the X-Arcade controller without crashing then ? If MAME OS X can do it, why SDLMAME couldn't ? No idea. Dumb luck? Chance? LN "When life gives you zombies... CHA-CHIK! ...you make zombie-ade!"

Re: SDLMAME and X-Arcade = crash Lord Nightmare #49706 05/01/09 07:53 AM
Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia Vas Crabb Very Senior Member
Vas Crabb Very Senior Member Joined: Feb 2004 Posts: 2,608 Likes: 315 Sydney, Australia	It's because MAME OS X doesn't try to read back every property. Most of them work, but some don't. You can work out which ones by single-stepping Dave Dribin's HID Explorer in a debugger until it hangs. You could then add a hack to SDL to recognise the X-Arcade and avoid the problematic properties.

Re: SDLMAME and X-Arcade = crash Vas Crabb #49796 05/04/09 09:52 AM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	as i wrote, it's not only with sdlmame. it crashes with single mac games, in my case. have you tried to connect x-arcade after sdlmame is launched, not before? it works for me (didn't test it in sdl), despite it's not a comfortable solution. Quote 1. fix the firmware anyway, i opened a support case with x-gaming and they say "Because the X-Arcade works just like a normal keyboard when connected to the computer, it doesn't have any firmware upgrades." i also asked about the usb adaptor, like geoman. waiting for the reply. Last edited by straycat; 05/04/09 09:54 AM.

Re: SDLMAME and X-Arcade = crash straycat #49840 05/04/09 10:07 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by straycat anyway, i opened a support case with x-gaming and they say "Because the X-Arcade works just like a normal keyboard when connected to the computer, it doesn't have any firmware upgrades." If they can't fix the firmware, they should fix the hardware then...

Re: SDLMAME and X-Arcade = crash Marc Mame #49866 05/05/09 11:34 AM
Joined: Mar 2007 Posts: 238 Providence, RI T The Flying Ape Senior Member
The Flying Ape Senior Member T Joined: Mar 2007 Posts: 238 Providence, RI	Quote they should fix the hardware "They" as in Apple, right? Because it "just works" on Microsoft Vista64 and any Linux distro -- and the controller is just AWESOME!! Sad, but you are just another victim of the "issue" with designer computers.

Re: SDLMAME and X-Arcade = crash The Flying Ape #49871 05/05/09 01:03 PM
Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA L Lord Nightmare Very Senior Member
Lord Nightmare Very Senior Member L Joined: Mar 2006 Posts: 1,080 Likes: 7 PA, USA	I'll bet if you enable usb debugging on linux it will spit out a TON of errors/warnings when using the x-arcade... The problem isn't JUST x-arcade's fault, its also Apple's fault since broken usb devices like the x-arcade should NOT be able to crash the usb stack. But the source of the problem is the 'broken' firmware on the x-arcade. LN "When life gives you zombies... CHA-CHIK! ...you make zombie-ade!"

Re: SDLMAME and X-Arcade = crash Lord Nightmare #49873 05/05/09 01:14 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Yeah. It's essentially SOP for things to be designed not to the actual standard but to Microsoft's (often sloppy) implementation of it. This is why it took Linux forever to get sleep to work - it's demonstrably broken in a different way in every BIOS out there, but always in a way that MS's implementation works. That said, USB HID is awfully simple and screwing that up takes very special un-talent on the part of X-Gaming.

Re: SDLMAME and X-Arcade = crash R. Belmont #49880 05/05/09 04:11 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	x-gaming support lastest reply to my mail. case closed for me. Quote He's referring to our USB adapter. (refering to al3ph on this thread: http://forum.arcadecontrols.com/index.php?topic=91572.0) We have 2 different X-Arcade generations. The 1st generation X-Arcade only had PS/2 support, but you could purchase a USB adapter separately. It's this adapter that he mentions in the forum. You can find it here under "USB PC/Mac Adapter": http://www.xgaming.com/adapters.shtml Our 2nd generation X-Arcade came with a different PC cable that had both PS/2 and USB connections. This cable is the one that's causing problems for a few Leopard users. This is an issue only with OSX Leopard (earlier versions of OSX work ok) and we're still trying to narrow down the problem and provide a better solution. For now, we suggest that you get the USB PC/Mac Adapter. i believe it can be leopard's problem, not apple's overall. leopard came with more than a handful of bugs/incompatibilities. i hope they try to contact apple at least to solve the problem together. i bought my x-arcade from a spanish online shop, not from x-gaming themselves so i can't demand a free usb adapter. i'll have to wait, frustrated, before i decide if i cash in for the adapter even if not knowing for sure if it will work. i dont wanna have to sell this baby. thanks guys. Last edited by straycat; 05/05/09 04:15 PM.

Re: SDLMAME and X-Arcade = crash straycat #49893 05/05/09 10:27 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Same goes for me... If the USB PC/Mac Adapter is the ultimate solution, they should give it for free or at least clearly specify on their site the controller won't work on OS X Leopard without it on purchase. You should try to ask them for a free adapter or at least a good rebate. Last edited by Marc Mame; 05/05/09 10:28 PM.

Re: SDLMAME and X-Arcade = crash The Flying Ape #49894 05/05/09 10:36 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by The Flying Ape Quote they should fix the hardware "They" as in Apple, right? Because it "just works" on Microsoft Vista64 and any Linux distro -- and the controller is just AWESOME!! Sad, but you are just another victim of the "issue" with designer computers. I really don't care who's fault. I'm a victim of buying a product advertised as Fully Mac OS X compatible. And Apple has nothing to do with it. Originally Posted by X-Gaming Web Site 100% Compatible With Any Operating System (XP, Vista, Mac�, Unix, Linux, etc)

Re: SDLMAME and X-Arcade = crash Marc Mame #49905 05/06/09 10:18 AM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	Quote You should try to ask them for a free adapter or at least a good rebate. Originally Posted By: X-Gaming Web Site 100% Compatible With Any Operating System (XP, Vista, Mac™, Unix, Linux, etc) in the original store i bought from, it's outta stock so i asked them if i'm entitled to a free adapter based on their compatibility claim. i'll let ya know.

Re: SDLMAME and X-Arcade = crash straycat #49912 05/06/09 05:22 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	no go. didn't buy from official international reseller so i'm entitled to zilt. if someone has any luck with the adapter, lemme know.

Re: SDLMAME and X-Arcade = crash straycat #49923 05/06/09 10:15 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	Originally Posted by straycat no go. didn't buy from official international reseller so i'm entitled to zilt. if someone has any luck with the adapter, lemme know. I bought it from SWOLFSOFT GmbH which they list as an international reseller: http://www.xgaming.com/htm/international.shtml So i'll contact them about a free adaptor and see what they have to say about it.

Re: SDLMAME and X-Arcade = crash Lord Nightmare #49956 05/08/09 12:42 AM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	I got a reply from X-Gaming that the Tankstick works with their USB Pc/Mac Adapter under OS X 10.5.6

Re: SDLMAME and X-Arcade = crash Geoman #49979 05/08/09 09:37 AM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Good news. Now, are they going to send one for free ?

Re: SDLMAME and X-Arcade = crash Marc Mame #49981 05/08/09 09:50 AM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	thanks geoman. i guess it should work for the solo too. yeah, if they send you one for free let us know if it really works. i'm still gonna try to contact the shop i bought from and ask if they had any complaints. nothing to lose. either way, can't help but feel conned. [edit] ^i finished newzealand story on the amiga. a hell of a game Last edited by straycat; 05/08/09 02:44 PM.

Re: SDLMAME and X-Arcade = crash straycat #50132 05/15/09 10:14 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	X-Gaming's answer regarding the required Mac/PC Adaptor: "We can send you a free adapter if you purchased your X-Arcade directly from Xgaming. However, since you purchased your X-Arcade from one of our official resellers, you will have to contact them. International resellers have different polices than Xgaming(as stated in the warranty) and may not supply a USB adapter replacement, but it's always a good idea to ask anyways. If they won't send a replacement, you will need to purchase the adapter."

Re: SDLMAME and X-Arcade = crash Geoman #50151 05/18/09 10:49 AM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	I contacted the German reseller and he will send me an adaptor for free!

Re: SDLMAME and X-Arcade = crash Geoman #50152 05/18/09 04:20 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Lucky man ! Please tell us back if it works as expected.

Re: SDLMAME and X-Arcade = crash Marc Mame #50154 05/18/09 04:28 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	FWIW, I've read in multiple places recently that the actual joysticks wear out very quickly on the X-Arcade stuff, so you might have been better off being unable to use it ;-)

Re: SDLMAME and X-Arcade = crash R. Belmont #50313 05/25/09 03:45 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	ok, i can't get a free or paid adaptor from spanish shop. also, i tried as last resort, to connect the x-solo to a simple usb hub and to the mac and even connect it on a fresh leopard 10.5.4 install. both still freeze my system with the applehid.plugin. without it, it freezes all the same whenever i launch an app. have to connect it after i launch the app. my original cable must be definately screwed. still would like to know if someone has any luck with the x-gaming adaptor. i'll probably have to sell it.

Re: SDLMAME and X-Arcade = crash straycat #51843 07/22/09 07:17 PM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	any news on the adapter, geoman? does it hog somethin'?

Re: SDLMAME and X-Arcade = crash straycat #51871 07/23/09 12:01 PM
Joined: Mar 2007 Posts: 238 Providence, RI T The Flying Ape Senior Member
The Flying Ape Senior Member T Joined: Mar 2007 Posts: 238 Providence, RI	Quote ... a fresh leopard 10.5.4 install Eh? What would compel you to do that? I saw countless ads of auto-backup so you never have to do "that PC" operation again. Quote it freezes all the same whenever i launch an app ... i'll probably have to sell it. Good luck re-selling the Mac then! Does this hardware allow you to try an "alternate OS" (live or install), like Sony PS3 does?

Re: SDLMAME and X-Arcade = crash The Flying Ape #51873 07/23/09 12:54 PM
Joined: May 2009 Posts: 2,223 Likes: 387 J Just Desserts Very Senior Member
Just Desserts Very Senior Member J Joined: May 2009 Posts: 2,223 Likes: 387	Originally Posted by The Flying Ape Good luck re-selling the Mac then! Does this hardware allow you to try an "alternate OS" (live or install), like Sony PS3 does? Yyyyes, it does... haven't you ever heard of Boot Camp?

Re: SDLMAME and X-Arcade = crash Just Desserts #51876 07/23/09 03:13 PM
Joined: Mar 2001 Posts: 17,239 Likes: 263 USA R R. Belmont Very Senior Member
R. Belmont Very Senior Member R Joined: Mar 2001 Posts: 17,239 Likes: 263 USA	Review the thread - TFA is trolling on behalf of X-Gaming and their moronic firmware mis-coders That said, AFAIK both Fedora 11 and Win7 will boot directly on EFI hardware without Boot Camp.

Re: SDLMAME and X-Arcade = crash R. Belmont #52019 07/27/09 10:53 AM
Joined: Apr 2009 Posts: 10 Portugal S straycat Member
straycat Member S Joined: Apr 2009 Posts: 10 Portugal	Originally Posted by The Flying Ape Eh? What would compel you to do that? I saw countless ads of auto-backup so you never have to do "that PC" operation again. a fresh install on an exteeernal hard drive. Originally Posted by The Flying Ape Good luck re-selling the Mac then! Does this hardware allow you to try an "alternate OS" (live or install), like Sony PS3 does? dude, i don't know one person who has ever swicthed from mac to pc. with all the headaches that the mac has spared me since i moved from pc, i could even just throw the x-arcade to the trash. alternate os? i have amiga os on my mac but why the hell do i need an alternate os to play my os x games? meanwhile, anyone had any luck with ps/2 to usb adapter? maybe the ps/2 end of the cable is not screwed as the usb. Last edited by straycat; 07/27/09 10:56 AM.

Re: SDLMAME and X-Arcade = crash straycat #59692 03/06/10 12:55 PM
Joined: Apr 2009 Posts: 11 Geoman Member
Geoman Member Joined: Apr 2009 Posts: 11	X-Arcade released an updated circuit board that should work with Macs. It sells for $29.90 and you must open your X-Arcade to replace the old board.

Re: SDLMAME and X-Arcade = crash Geoman #59787 03/07/10 04:43 PM
Joined: Sep 2000 Posts: 286 Paris, France Marc Mame Senior Member
Marc Mame Senior Member Joined: Sep 2000 Posts: 286 Paris, France	Originally Posted by Geoman X-Arcade released an updated circuit board that should work with Macs. It sells for $29.90 and you must open your X-Arcade to replace the old board. Can you provide a link to that news ?

Page 1 of 12

…

Moderated by R. Belmont

Link Copied to Clipboard