RE: State of threads in crash log
RE: State of threads in crash log
- Subject: RE: State of threads in crash log
- From: "Crichlow, Eric" <email@hidden>
- Date: Thu, 21 Aug 2003 13:20:01 -0400
>
> Thread 2:
>
> #0 0x90073c48 in mach_msg_trap
>
> #1 0x90005f90 in mach_msg
>
> #2 0x90007698 in vm_deallocate
>
> #3 0x9005e428 in _pthread_reap_thread
>
> #4 0x90026cc0 in _pthread_reap_threads
>
> #5 0x90026a28 in pthread_exit
>
> #6 0x97e2cc60 in forkThreadForFunction
>
> #7 0x90020d48 in _pthread_body
>
>
This is not a list of threads, but a stack trace in a thread.
>
>
It means that when your app crached, thread 2 was executing
>
function mach_msg_trap, called from mach_msg called from
>
vm_deallocate .....
Yes, the piece of the log I posted is a stack trace for a single thread.
What I am saying is that I have a crashlog that has 68 such entries that
are exactly the same (except, of course, for the thread number).
So I'm questioning whether or not I have 68 threads that haven't
finished exiting for some reason (they're all in "pthread_exit") or if they
all did finish exiting and these entries exist just to show me that these
threads once existed and exited successfully.
...Eric...
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.