Re: Mystery threads eating CPU cycles
Re: Mystery threads eating CPU cycles
- Subject: Re: Mystery threads eating CPU cycles
- From: Douglas Davidson <email@hidden>
- Date: Mon, 11 Nov 2002 11:34:39 -0800
On Monday, November 11, 2002, at 11:25 AM, Mike Laster wrote:
Probably so, but the original signal that started this probably would
otherwise have been fatal. It seems likely that the odd stack traces
you are getting from sample are confused because of the signals;
these probably are ordinary threads, just with incomplete backtraces.
Try turning off ExceptionHandling signal handling, running in gdb,
and trying to locate the source of the original signal.
I'm sure they are incomplete. Sample floods stdout with:
sample[3130] thread_read_stack: stack appears to be in inconsistent
state to trace. Truncating stack.
Whenever I try to get a sample of the running process.
I haven't been able to reproduce this problem on my development
machine. The machine that it is running on doesn't have a development
environment, so no gdb.
Does the ExceptionHandling framework spawn off private threads for
doing it's own work...could that be where these new threads are coming
from that I didn't create?
No, it does not.
How do you know you didn't create these threads? From the stack
traces? That's not evidence; the traces are corrupt. Is it because
you never spawn threads? There are cases in which frameworks spawn
threads for their own purposes; try looking at a sample from a
correctly running instance to see what those might be.
Douglas Davidson
_______________________________________________
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.