From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Luke <hazelnusse@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: -ggdb3 -gdwarf-4 but "info macro BLAH" still doesn't work?
Date: Tue, 08 May 2012 10:52:00 -0000 [thread overview]
Message-ID: <20120508105150.GA14311@host2.jankratochvil.net> (raw)
In-Reply-To: <CAEQ-UNe4TOemQ0u7k90GrddERceEbiW1juTckkgVCc79W0zdXA@mail.gmail.com>
On Tue, 08 May 2012 12:03:50 +0200, Luke wrote:
> $ gcc -gdwarf-4 -gdb3 -Wall -O0 sample.c -o sample
-ggdb3, otherwise:
cc1: error: unrecognised debug output level "db3"
> This happens with Linaro gcc 4.7-2012.04, as well as a very recent
> pull from gcc master (4.8.0 20120502).
>
> It doesn't happen with gcc 4.6.2.
It is probably due to the smaller .debug_macro section by Jakub Jelinek.
See 'readelf -WS sample', .debug_macinfo is the gdb-7.4.x compatible format,
.debug_macro is the new format available only in post-7.4 GDB snapshots since:
commit 101e95e8a31879712dff26d233cdb266c1aba673
Author: Tom Tromey <tromey@redhat.com>
Date: Tue Jul 26 17:04:21 2011 +0000
You can request with new GCC the old .debug_macinfo format by -gstrict-dwarf
but it also generates more poor debug info in other regards.
> Any suggestions? I'm guessing this is a gcc bug.
Use GDB snapshot:
http://sources.redhat.com/gdb/current/
Regards,
Jan
next prev parent reply other threads:[~2012-05-08 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 10:04 Luke
2012-05-08 10:52 ` Jan Kratochvil [this message]
2012-05-08 10:55 ` Jan Kratochvil
-- strict thread matches above, loose matches on Subject: below --
2012-05-01 20:37 Martin Olsson
2012-05-01 21:56 ` Matt Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120508105150.GA14311@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=hazelnusse@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox