public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/99457] gcc/gdb -gstabs+ is buggy.
Date: Mon, 08 Mar 2021 08:52:26 +0000 [thread overview]
Message-ID: <bug-99457-4-N0onezYacP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99457-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99457
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can't reproduce (not that anyone would care) with either current 9 branch or
current trunk, there is no reason not to use DWARF.
Sure, on the line that defines the variable you can see garbage in the variable
because it is not initialized yet and STABS has no way to express that (though,
with -O0 gcc doesn't track that anyway), but on the following line which you
get after b main r n it shows the var to be all zeros.
next prev parent reply other threads:[~2021-03-08 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 4:49 [Bug debug/99457] New: " jay.krell at cornell dot edu
2021-03-08 5:27 ` [Bug debug/99457] " pinskia at gcc dot gnu.org
2021-03-08 5:29 ` pinskia at gcc dot gnu.org
2021-03-08 8:52 ` jakub at gcc dot gnu.org [this message]
2021-03-08 9:26 ` jay.krell at cornell dot edu
2021-03-08 9:58 ` rguenth 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-99457-4-N0onezYacP@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).