public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28987] Outdated value being displayed for variable while DWARF info apparently contains the correct one Date: Sat, 09 Apr 2022 15:17:57 +0000 [thread overview] Message-ID: <bug-28987-4717-rCyhyKjS64@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28987-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28987 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2022-04-09 CC| |tromey at sourceware dot org Status|UNCONFIRMED |NEW --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I can reproduce. I see this: (gdb) info addr i Symbol "i" is multi-location: Base address 0x201140 Range 0x201140-0x201140: the constant 0 Range 0x201140-0x201140: the constant 1 Range 0x201140-0x201140: the constant 2 Range 0x201140-0x201140: the constant 3 Range 0x201140-0x201140: the constant 4 Range 0x201140-0x201140: the constant 5 Range 0x201140-0x201140: the constant 6 Range 0x201140-0x201140: the constant 7 Range 0x201140-0x201151: the constant 8 . (gdb) p $pc $2 = (void (*)()) 0x201140 <foo> I think this falls into this case in dwarf2/loc.c: if (low == high && pc == low) { /* This is entry PC record present only at entry point of a function. Verify it is really the function entry point. */ I don't really know why this code is exactly here. Like, it has to do with computing entry values, but I don't know why it's needed. If I comment out that block, this test case works. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-09 15:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-21 19:44 [Bug gdb/28987] New: " assaiante at diag dot uniroma1.it 2022-04-09 15:17 ` tromey at sourceware dot org [this message] 2023-03-27 20:48 ` [Bug gdb/28987] " tromey at sourceware dot org 2023-04-06 17:58 ` hluaw at connect dot ust.hk 2023-12-16 10:28 ` cvs-commit at gcc dot gnu.org 2023-12-16 10:30 ` ssbssa at sourceware dot org 2024-10-14 13:33 ` vries at gcc dot gnu.org 2024-10-14 17:31 ` sam at gentoo dot 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-28987-4717-rCyhyKjS64@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).