Re: Diagnosing corrupted stacks
Re: Diagnosing corrupted stacks
- Subject: Re: Diagnosing corrupted stacks
- From: John Engelhart <email@hidden>
- Date: Fri, 1 May 2009 16:18:51 -0400
On Fri, May 1, 2009 at 12:23 PM, Tom McHale
<email@hidden> wrote:
You are right, that brings my machine to its knees even with a reasonable ring buffer and limiting to one CPU.
What to do? It would be nice to surgically strike the frameworks I am using and do the probes a couple at a time.
You could give this a shot:
---
#!/usr/bin/dtrace -s
#pragma D option quiet
#pragma D option zdefs
#pragma D option bufpolicy=ring
#pragma D option bufsize=64k
pid$target::aeDispatchAppleEvent*:entry { ustack(); }
---
This would log, in a ring buffer, a full stack back trace on every entry in to aeDispatchAppleEvent* (dtrace accepts '*' wildcard matching). Hopefully the stack isn't smashed on entry and you can get an idea of 'where' things are going wrong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden