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 testsuite/30553] New: [gdb/testsuite] FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited) Date: Wed, 14 Jun 2023 14:45:22 +0000 [thread overview] Message-ID: <bug-30553-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30553 Bug ID: 30553 Summary: [gdb/testsuite] FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On powerpc64-linux (CentOS 7), I run into: ... (gdb) PASS: gdb.base/sym-file.exp: info files must display sym-file-lib continue^M Continuing.^M [Inferior 1 (process 60062) exited with code 01]^M (gdb) FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited) ... After some debugging, I found it's due to this returning: ... /* Call bar from SHLIB_NAME. */ if (lookup_function (lib, "bar", (void *) &pbar) != 0) return 1; ... rather than continuing and executing: ... (*pbar) (); ... which would have triggered the breakpoint. The test-case contains some dlsym implementation. It could be already confused by bar being a D symbol in the .opd section, rather than a T symbol in the .text section. But AFAICT, the loaded symbol table contains garbage, so possibly it's a little-endian only implementation. It makes me wonder why dlsym is not used. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-06-14 14:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30553-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).