Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
macOS & iOS Developer Playground
macOS - Development and Darwin
Memory leak/error tool for OS X?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="miggles" data-source="post: 45075" data-attributes="member: 5662"><p>I use Rational Purify all the time at work, but it's only available for SunOS, Irix, redhat, and windows. Can anyone recommend a similar tool for OS X? I have seen a code called OmniObjectMeter, but it looks like it can only handle full-fledged applications which have been linked through Project Builder, not simple command line linked applications (e.g. an a.out which links in nothing and prints "hello world" to the terminal).</p><p></p><p>Also, I have a long standing problem with debug-compiled (-g) objects which essentially makes gdb inconvenient and useless. Whenever I enter gdb, I always have to provide it the directories where the original source code objects are located. This is not trivial when I am linking in several dozen libraries or building different variants of codes under different source trees. Is there a way for gcc to encode the full paths into the objects to make gdb less cumbersome?</p><p></p><p>Thanks.</p></blockquote><p></p>
[QUOTE="miggles, post: 45075, member: 5662"] I use Rational Purify all the time at work, but it's only available for SunOS, Irix, redhat, and windows. Can anyone recommend a similar tool for OS X? I have seen a code called OmniObjectMeter, but it looks like it can only handle full-fledged applications which have been linked through Project Builder, not simple command line linked applications (e.g. an a.out which links in nothing and prints "hello world" to the terminal). Also, I have a long standing problem with debug-compiled (-g) objects which essentially makes gdb inconvenient and useless. Whenever I enter gdb, I always have to provide it the directories where the original source code objects are located. This is not trivial when I am linking in several dozen libraries or building different variants of codes under different source trees. Is there a way for gcc to encode the full paths into the objects to make gdb less cumbersome? Thanks. [/QUOTE]
Verification
Name this item 🌈
Post reply
Forums
macOS & iOS Developer Playground
macOS - Development and Darwin
Memory leak/error tool for OS X?
Top