[Valgrind-users] stack traces lack source file name & line number on Mac OS X 10.5

[Sean M. <se...@ro...>]

Hi all,

I'm not seeing source file names and line numbers running memcheck on
Mac OS X 10.5.8.  After some investigation I determined valgrind does
not deal well with spaces in path names. :(

If I do:

valgrind /Users/sean/Desktop/Valgrind\ Test/build/Debug/Valgrind\ Test.app

It complains:

--7764-- run: /usr/bin/dsymutil /Users/sean/Desktop/Valgrind Test/build/
Debug/Valgrind Test.app/Contents/MacOS/Valgrind Test
error: unable to open executable '/Users/sean/Desktop/Valgrind'

and then I get backtraces like:

...
==7655==    by 0xD451D7: NSApplicationMain (in /System/Library/
Frameworks/AppKit.framework/Versions/C/AppKit)
==7655==    by 0x1FFB: main (in /Users/sean/Desktop/ValgrindTest/build/
Debug/ValgrindTest.app/Contents/MacOS/ValgrindTest)

Using --dsymutil=yes does not help.

Is this a known bug?  Is there a workaround (other than 'don't use spaces')?

Thanks,

-- 
____________________________________________________________
Sean McBride, B. Eng                 se...@ro...
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada