On 4 Dec 2012, at 11:48, Gerriet M. Denkmann <gerr...@mdenkmann.de> wrote:
> > On 4 Dec 2012, at 18:10, Roland King <r...@rols.org> wrote: > >> Can you not run Instruments from the 'Profile' button on Xcode? It should >> start the process and attach to it and go from there. > > I got the Leaks Instrument to work this way (no Leaks) But all other > Instruments just prompted repeatedly for an admin password but did not do > anything at all. > > Activity Monitor gave me a Sample. Here is the main thread: > > Call graph: > 1343 Thread_3102216 DispatchQueue_1: com.apple.main-thread (serial) > + 1343 start (in libdyld.dylib) + 1 [0x7fff983887e1] > + 1343 NSApplicationMain (in AppKit) + 869 [0x7fff96809cb6] > + 1343 -[NSApplication run] (in AppKit) + 517 [0x7fff96865283] > + 1343 -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit) + 128 > [0x7fff9686ded2] > + 1343 _DPSNextEvent (in AppKit) + 685 [0x7fff9686e613] > + 1343 BlockUntilNextEventMatchingListInMode (in HIToolbox) + 62 > [0x7fff90ec2cd3] > + 1343 ReceiveNextEventCommon (in HIToolbox) + 217 > [0x7fff90ec2db7] > + 1343 AcquireEventFromQueue (in HIToolbox) + 561 > [0x7fff90eccf8f] > + 1343 _NotifyEventLoopObservers (in HIToolbox) + 155 > [0x7fff90e9b6e0] > + 1343 HIApplication::EventObserver(unsigned int, > OpaqueEventRef*, void*) (in HIToolbox) + 193 [0x7fff90ecd407] > + 1343 HIApplication::HandleActivated(OpaqueEventRef*, > unsigned char, OpaqueWindowPtr*) (in HIToolbox) + 177 [0x7fff90ecfe0f] > + 1343 SetMenuBarObscured (in HIToolbox) + 221 > [0x7fff90ed0144] > + 1343 MenuBarInstance::Show(MenuBarAnimationStyle, > unsigned char, unsigned char, unsigned char) (in HIToolbox) + 625 > [0x7fff90ea5063] > + 1343 BroadcastToolboxMessage (in HIToolbox) + > 294 [0x7fff90e6e12a] > + 1343 > HIS_XPC_CFNotificationCenterPostNotification (in HIServices) + 532 > [0x7fff8e57f174] > + 1343 CFNotificationCenterPostNotification > (in CoreFoundation) + 115 [0x7fff95edbbf3] > + 1343 _CFXNotificationPost (in > CoreFoundation) + 1109 [0x7fff95ecced5] > + 1343 -[_NSDNXPCConnection > sendMessage:waitForAck:] (in CoreFoundation) + 347 [0x7fff95fec12b] > + 1343 _dispatch_semaphore_wait_slow > (in libdispatch.dylib) + 241 [0x7fff97ed0486] > + 1343 semaphore_wait_trap (in > libsystem_kernel.dylib) + 10 [0x7fff95ac86c2] > > > I have no idea, what this means. > Maybe someone can enlighten me. > > Gerriet. > Your app is blocking waiting for a semaphore. The extract below is from http://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/KernelProgramming/synchronization/synchronization.html A semaphore is much like a lock, except that a finite number of threads can hold it simultaneously. Semaphores can be thought of as being much like piles of tokens. Multiple threads can take these tokens, but when there are none left, a thread must wait until another thread returns one. It is important to note that semaphores can be implemented in many different ways, so Mach semaphores may not behave in the same way as semaphores on other platforms. It looks as if part of the menu system needs a particular semaphore which is currently blocked as a result of other operations. I don't have a solution but the following is related. http://stackoverflow.com/questions/13148684/deadlock-using-dispatch-semaphore-t-in-a-concurrent-queue Jonathan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
