public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/26800] New: [readnow] symtabs not expanded when re-reading Date: Wed, 28 Oct 2020 12:19:36 +0000 [thread overview] Message-ID: <bug-26800-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26800 Bug ID: 26800 Summary: [readnow] symtabs not expanded when re-reading Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- There's a group of FAILs with -readnow: ... FAIL: gdb.ada/exec_changed.exp: start second FAIL: gdb.ada/exec_changed.exp: start just first FAIL: gdb.base/reread.exp: opts= "" "" : run to foo() second time FAIL: gdb.base/reread.exp: opts= "" "" : second pass: run to foo() second time FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : run to foo() second time FAIL: gdb.base/reread.exp: opts= "-fPIE" "ldflags=-pie" : second pass: run to foo() second time ... This FAIL: ... FAIL: gdb.base/reread.exp: opts= "" "" : run to foo() second time ... can be reproduced a follows. First, run the test-case. Then rename the reread exec to the original name: ... $ mv outputs/gdb.base/reread/reread outputs/gdb.base/reread/reread2 ... such that we have: ... $ ls -1 outputs/gdb.base/reread/reread* outputs/gdb.base/reread/reread1 outputs/gdb.base/reread/reread2 ... Then, do a run without -readnow for contrast: ... $ gdb -batch \ -ex "shell cp outputs/gdb.base/reread/reread1 reread" \ -ex "file reread" \ -ex "b foo" \ -ex run \ -ex "shell rm reread" \ -ex "shell cp outputs/gdb.base/reread/reread2 reread" \ -ex "shell sleep 1" \ -ex run Breakpoint 1 at 0x654: file /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/reread1.c, line 14. Breakpoint 1, foo () at /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/reread1.c:14 14 x++; `/home/vries/gdb_versions/devel/reread' has changed; re-reading symbols. Breakpoint 1, foo () at /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/reread2.c:9 9 x++; ... Note that the second time we hit foo, it shows foo at reread2.c:9. With -readnow however, the second time we hit foo, no file/lineno is shown: ... Breakpoint 1 at 0x654: file /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/reread1.c, line 14. Breakpoint 1, foo () at /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/reread1.c:14 14 x++; `/home/vries/gdb_versions/devel/reread' has changed; re-reading symbols. Breakpoint 1, 0x000055555555468e in foo () ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-10-28 12:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-28 12:19 vries at gcc dot gnu.org [this message] 2020-10-28 12:21 ` [Bug symtab/26800] " vries at gcc dot gnu.org 2020-11-01 17:44 ` tromey at sourceware dot org 2021-10-11 14:56 ` vries at gcc dot gnu.org 2021-12-07 6:53 ` vries 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-26800-4717@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).