Building toolchain libraries with debugging symbols
Bryan Hundven
bryanhundven@gmail.com
Fri Mar 4 01:03:00 GMT 2016
> On Mar 3, 2016, at 3:26 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>
>>
>> On Mar 3, 2016, at 11:26 AM, Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
>>
>> On Mon, Feb 8, 2016 at 10:40 AM, Thomas De Schampheleire
>> <patrickdepinguin@gmail.com> wrote:
>>> Hello,
>>>
>>> What is the 'correct' way to make sure that the libraries of the
>>> toolchain (most importantly libc but possibly others) contain
>>> debugging symbols, so that debugging an application linked to these
>>> libraries works as expected?
>>>
>>> Toolchains provided by external vendors are configured as such, but it
>>> seems that crosstool-ng by default does not.
>>>
>>> We did not find a global setting for this. As a workaround we applied
>>> the following:
>>>
>>> CT_LIBC_GLIBC_EXTRA_CFLAGS="-g"
>>>
>>> but it is unclear if this is the 'correct' way or not.
>>>
>>
>> ping?
>
> Thomas,
>
> Sorry for the delay, I just saw this email. I’m not sure why I didn’t see the earlier email.
>
> I need to do a little research, but I’ve CC’d Yann E. Morin in case he knows off hand.
> If not, I’ll have a response soon.
>
> Cheers,
>
> -Bryan
I think it’s fairly accurate to say that there isn’t a global setting, and it seems to be libc specific.
So there isn’t a configuration setting besides the one you noted for glibc.
For uClibc(-ng), there is CT_LIBC_UCLIBC_DEBUG_LEVEL.
And I’m guessing the same solution for glibc for musl-libc and newlib.
It would be fairly simple to add debugging options to the other LIBCs so they also have debugging options.
-Bryan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20160304/ba892c3b/attachment.sig>
More information about the crossgcc
mailing list