public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug tdep/31089] New: [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main
@ 2023-11-27 17:00 vries at gcc dot gnu.org
  2024-06-07  8:15 ` [Bug tdep/31089] " vries at gcc dot gnu.org
  2024-06-07 12:01 ` vries at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-11-27 17:00 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=31089

            Bug ID: 31089
           Summary: [gdb/tdep, arm] FAIL:
                    gdb.base/longjmp-until-in-main.exp: until $line, in
                    main
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On a pinebook, I ran into:
...
(gdb) until 33^M
Warning:^M
Cannot insert breakpoint 0.^M
Cannot access memory at address 0x0^M
^M
0xf76d57e8 in siglongjmp () from /lib/arm-linux-gnueabihf/libc.so.6^M
(gdb) FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main
...

This is a partly a duplicate of PR26967, in the sense that the longjmp target
is mangled.

But there is another problem: it's read from the wrong offset (hence address
0x0).  

The tdep->jb_pc value is 9, but the actual value seems to be 1.  See
./sysdeps/arm/setjmp.S from glibc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug tdep/31089] [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main
  2023-11-27 17:00 [Bug tdep/31089] New: [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main vries at gcc dot gnu.org
@ 2024-06-07  8:15 ` vries at gcc dot gnu.org
  2024-06-07 12:01 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2024-06-07  8:15 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=31089

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
https://sourceware.org/pipermail/gdb-patches/2024-June/209738.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug tdep/31089] [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main
  2023-11-27 17:00 [Bug tdep/31089] New: [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main vries at gcc dot gnu.org
  2024-06-07  8:15 ` [Bug tdep/31089] " vries at gcc dot gnu.org
@ 2024-06-07 12:01 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2024-06-07 12:01 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=31089

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |16.1

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by commit 1a7d840a216 ("[gdb/tdep] Fix ARM_LINUX_JB_PC_EABI").

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-06-07 12:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-27 17:00 [Bug tdep/31089] New: [gdb/tdep, arm] FAIL: gdb.base/longjmp-until-in-main.exp: until $line, in main vries at gcc dot gnu.org
2024-06-07  8:15 ` [Bug tdep/31089] " vries at gcc dot gnu.org
2024-06-07 12:01 ` vries at gcc dot gnu.org

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).