Subject: Re: [Boost-build] debug build with -g and -O0 ?
From: Nogradi, Chris (Chris.Nogradi_at_[hidden])
Date: 2012-04-26 08:11:35
should have done what you wanted. The default is debug also so:
would have been good.
From: boost-build-bounces_at_[hidden] [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Manuel Dejonghe
Sent: Wednesday, April 25, 2012 1:55 PM
Subject: [Boost-build] debug build with -g and -O0 ?
I am currently investigating a problem where I would need the boost
debug build to be built with "-g -O0". I ran a build with
"variant=debug" and getting clearly binaries with are bigger in size,
but my problem persist, and I wonder where I would have to check (or
modify) the b2/jam-stuff to make sure this is included.
My setup is that I wrote a unit test with boost test, and when I am
running it through (or rather with) valgrind, I still get unknown
symbols. From how I read the callstack, this clearly must be whatever
calls the API to be unit tested, hence boost test.
Or is it maybe known that the boost c++ kung-fu is so much
sophisticated that valgrind can't properly resolve the symbols ? (I
did not ask on the valgrind list yet tho)
many thanks for any pointers,
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.
Thank you for your cooperation.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk