Re: Re: Using Sampler
Re: Re: Using Sampler
- Subject: Re: Re: Using Sampler
- From: "Alan Smith" <email@hidden>
- Date: Wed, 27 Sep 2006 20:27:56 -0400
Right, but I don't think there is a way to get this info via Sampler. You
have to use gdb.
Also remember that Sampler/Shark won't tell you every call that happened.
It'll tell you about the calls that took a significant amount of time, but
if you are trying to reverse engineer something, there are probably going to
be some steps which don't show up via the Sampler approach (because they
happen quickly or rarely) but are still highly important.
So, what do you suggest? I'm relatively new to reverse engineering but
have done some. I'm not what you would call a noob but I'm not an
expert either.
Thank you all for the help thus far, Alan
On 9/27/06, John Stiles <email@hidden> wrote:
On Sep 27, 2006, at 4:16 PM, Nick Zitzmann wrote:
On Sep 27, 2006, at 4:47 PM, Alan Smith wrote:
In *addition* to the function calls, I want to know what is being
passed to each method/function.
If you're using a PPC Mac, then AFAIK you can only acquire the arguments
passed into the current top of the stack. They are stored in registers $r3,
$r4, and so on.
If you're using an Intel Mac, then arguments are stored in the stack (at
least on IA-32), and you can acquire them by examining registers $ebp+8,
$ebp+12, and so on.
Right, but I don't think there is a way to get this info via Sampler. You
have to use gdb.
Also remember that Sampler/Shark won't tell you every call that happened.
It'll tell you about the calls that took a significant amount of time, but
if you are trying to reverse engineer something, there are probably going to
be some steps which don't show up via the Sampler approach (because they
happen quickly or rarely) but are still highly important.
--
// Quotes from yours truly -------------------------
"You don't forget, you just don't remember."
"Maturity resides in the mind."
"Silence is the Universe's greatest gift."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden