• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: tracing a process
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tracing a process


  • Subject: Re: tracing a process
  • From: Markian Hlynka <email@hidden>
  • Date: Thu, 17 Feb 2005 19:16:04 -0700


On Feb 17, 2005, at 18:25, Mike Lazear wrote:


On Feb 17, 2005, at 5:00 PM, Markian Hlynka wrote:

Hi.

I'm trying to trace a running app to figure out what call stack it's embarking on that's making it behave undesirably. I'm looking for a tool, kind of like ktrace, but one that will give me application calls. I know Shark and Saturn exist, but I'm not sure they're the right tool for the job, as I don't want a profile, but rather a callstack for a snapshot in time. Can anyone make any suggestions?


The upper left hand section of the debugger window in XCode is a Call Stack, is there some reason you aren't using that?

yup, there's a reason. I mean, I don't know where the problem is. So, by the time I hit "pause", the moment has gone by. I can put breakpoints, but the purpose of this exercise is to determine where to put them. Plus, I'm attaching to a running process with gdb. And, the code for the executable seems to have disappeared. At least, no one seems to have it. I think maybe I changed a file format somewhere, which is why I'm getting weird behaviour. So, I want to attach to the executable and determine what the call stack is when I invoke the 'bad stuff'. I just need to get an idea of where to put the breakpoints in gdb so I can narrow down the field.



Thanks!

_______________________________________________
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


References: 
 >tracing a process (From: Markian Hlynka <email@hidden>)
 >Re: tracing a process (From: Mike Lazear <email@hidden>)

  • Prev by Date: Re: tracing a process
  • Next by Date: dumb question, quick solution needed
  • Previous by thread: Re: tracing a process
  • Next by thread: Re: tracing a process
  • Index(es):
    • Date
    • Thread