Subject: Re: [Boost-build] Adding debuglink information
From: Anthony Foglia (AFoglia_at_[hidden])
Date: 2010-02-23 19:16:07
Sorry for the initial message, but after further examination it appears
to be unrelated to Boost or Boost.Build.
I was basing my initial message on the problems of a team member and my
won Googling about GDB. (I'm not nearly as familiar with it as I should
be.) After sending the initial message, as a test on my own, I stepped
through the first example from the program options library in the
debugger. It couldn't find the cpp files (no surprise) but did print
out the line number.
There was a problem if I stepped to far into the code to configure the
options: eventually ddd was looking for value_semantic.hpp in the wrong
place (although it had already stepped through the right one previously).
Since the original user was using Eclipse (which is why I don't even
know the GDB messages), we now believe this is more an Eclipse issue
than anything else.
Vladimir Prus wrote:
> Anthony Foglia wrote:
>> And second: How do I do this in boost-build? It doesn't call objcopy
>> by default, nor does it seem any of the default features would do it.
> It is not presently supported to generate separate debug info. You can
> file an issue in Trac to have it considered for future versions.
It should probably be considered, but there's no pressing use case. (I
could see it useful for distributions compiling boost from source.)
Should I add an issue in Trac just so there's a record?
Sorry for the trouble
-- Anthony Foglia Princeton Consultants (609) 987-8787 x233
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