Re: Dtrace for tracing memory frees
Re: Dtrace for tracing memory frees
- Subject: Re: Dtrace for tracing memory frees
- From: Jakub Bednar <email@hidden>
- Date: Thu, 3 Jul 2008 14:36:14 +0200
Thanks a lot,
it seems I finally have all the data I need.
Regards,
Jakub
On Jul 2, 2008, at 7:40 PM, Ken Thomases wrote:
On Jul 2, 2008, at 11:23 AM, Jakub Bednar wrote:
I used XCode-3.1 to build the tool. I run it in Object Allocations
and it
probably doesn't crash, because no error message or Crash Reporter
window showed. Or how should I get the crash report?
Well, a GUI application would produce a crash report. By default, a
command-line tool does not. You can change that using /Developer/
Applications/Utilities/CrashReporterPrefs.app.
Also, when you run a program using Instruments, its output goes to /
dev/console. You can check it using /Applications/Utilities/
Console.app.
I've tried attaching gdb to the process created by Object
Allocations.
But it shows that executable ended normally.
Weird. I don't know why that would be happening.
I've also another question. I know how to set environment variables
when running executable from instruments. But how can I set them
when running from XCode and XCode-Debugger.
In the project window, find the Executables file group. (Where this
is depends on how you configured Xcode's interface.) Under that
group, find the executable of interest. Double-click it to open its
Info window. On the Arguments tab, you can provide command-line
arguments and environment variables.
Cheers,
Ken
_______________________________________________
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