public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/100446] GDB has problems reading GCC's debugging info level -g3 Date: Thu, 06 May 2021 11:14:52 +0000 [thread overview] Message-ID: <bug-100446-4-MHM3tdrfY3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100446-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100446 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|other |debug Keywords| |lto CC| |rguenth at gcc dot gnu.org See Also| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=27754 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I commented on the gdb issue, since -flto/-fno-lto have comparable .debug_macro the issue must lie with gdb. Sorry for just shifting the blame ;)
next prev parent reply other threads:[~2021-05-06 11:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-06 10:33 [Bug other/100446] New: " rdiezmail-gcc at yahoo dot de 2021-05-06 11:14 ` rguenth at gcc dot gnu.org [this message] 2021-05-06 11:33 ` [Bug debug/100446] " rguenth at gcc dot gnu.org 2021-05-06 11:43 ` rdiezmail-gcc at yahoo dot de 2021-05-06 11:51 ` rguenth at gcc dot gnu.org 2021-05-06 12:31 ` rdiezmail-gcc at yahoo dot de 2021-05-10 20:33 ` tromey at gcc dot gnu.org 2021-05-12 20:49 ` simon.marchi at polymtl dot ca 2022-04-19 20:55 ` tromey at gcc dot gnu.org
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=bug-100446-4-MHM3tdrfY3@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).