public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31268] New: gdb.base/unwind-on-each-insn-amd64.exp regression Date: Fri, 19 Jan 2024 15:42:20 +0000 [thread overview] Message-ID: <bug-31268-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31268 Bug ID: 31268 Summary: gdb.base/unwind-on-each-insn-amd64.exp regression Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simark at simark dot ca Target Milestone: --- I see: FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: $fba_value == $fn_fba FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: check frame-id matches FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: bt 2 FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: up FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: $sp_value == $::main_sp FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: $fba_value == $::main_fba FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: [string equal $fid $::main_fid] Tom Tromey said he was only able to reproduce with an ASan build, so it might be important here, even though gdb.log doesn't contain an ASan error. The first error is: 380 (gdb) PASS: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: get $sp and frame base for fn: get hexadecimal valueof "$sp" 381 info frame^M 382 Stack level 0, frame at 0x7fffffffd5a0:^M 383 rip = 0x40112f in foo (/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/unwind-on-each-insn-foo.c:22); saved rip = 0x7ffff7df01ca^M 384 called by frame at 0x7fffffffd640^M 385 source language c.^M 386 Arglist at 0x7fffffffd590, args: s=0x401114 <main+14> "\277\b @"^M 387 Locals at 0x7fffffffd590, Previous frame's sp is 0x7fffffffd5a0^M 388 Saved registers:^M 389 rbp at 0x7fffffffd590, rip at 0x7fffffffd598^M 390 (gdb) FAIL: gdb.base/unwind-on-each-insn-amd64.exp: foo: instruction 6: $fba_value == $fn_fba -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-19 15:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 15:42 simark at simark dot ca [this message] 2024-01-19 15:42 ` [Bug gdb/31268] " simark at simark dot ca 2024-01-20 14:52 ` vries at gcc dot gnu.org 2024-01-20 14:52 ` vries at gcc dot gnu.org 2024-01-20 14:53 ` vries at gcc dot gnu.org 2024-01-21 10:43 ` vries at gcc dot gnu.org 2024-03-27 14:26 ` vries at gcc dot gnu.org 2024-03-27 14:29 ` vries at gcc dot gnu.org 2024-04-01 7:56 ` vries at gcc dot gnu.org 2024-04-02 12:04 ` [Bug symtab/31268] " vries at gcc dot gnu.org 2024-04-08 13:06 ` vries at gcc dot gnu.org 2024-04-14 18:03 ` brobecker at gnat dot com 2024-04-15 11:48 ` vries at gcc dot gnu.org 2024-04-24 14:27 ` cvs-commit at gcc dot gnu.org 2024-04-24 21:12 ` 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-31268-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).