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/26967] New: FAIL: gdb.base/longjmp.exp: next over longjmp(1) Date: Sat, 28 Nov 2020 12:44:37 +0000 [thread overview] Message-ID: <bug-26967-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26967 Bug ID: 26967 Summary: FAIL: gdb.base/longjmp.exp: next over longjmp(1) 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 SLE-11, I ran into: ... FAIL: gdb.base/longjmp.exp: next over longjmp(1) ... In more detail: ... (gdb) next^M 52 longjmp (env, 1);^M (gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1) next^M 56 resumes++;^M (gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1) ... What is expected: ... (gdb) next^M 52 longjmp (env, 1);^M (gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1) next^M 0x00000000004005cc 49 if (setjmp (env) == 0) /* patt1 */^M (gdb) PASS: gdb.base/longjmp.exp: next over longjmp(1) ... I've analyzed this behaviour to be caused by the lack of presence of longjmp probes in libc. On SLE-11, we have glibc-2.11.3, the probes were added in 2.16 for x86_64. I can reproduce the same behaviour with a current glibc by forcing probe_safe_evaluate_at_pc to return NULL (which makes you wonder whether a gdb command probes ignore could be useful). -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-11-28 12:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-28 12:44 vries at gcc dot gnu.org [this message] 2021-01-08 14:28 ` [Bug testsuite/26967] " vries at gcc dot gnu.org 2021-01-27 15:17 ` vries at gcc dot gnu.org 2022-12-05 23:33 ` tromey at sourceware dot org 2022-12-07 8:33 ` vries at gcc dot gnu.org 2022-12-07 10:31 ` vries at gcc dot gnu.org 2022-12-07 10:36 ` vries at gcc dot gnu.org 2022-12-07 15:10 ` vries at gcc dot gnu.org 2022-12-07 15:45 ` cvs-commit at gcc dot gnu.org 2024-03-20 18:24 ` cvs-commit 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-26967-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).