[Bug breakpoints/22567] New: pending breakpoint location's gdbarch is incorrect after it is resolved

["qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 22567
           Summary: pending breakpoint location's gdbarch is incorrect
                    after it is resolved
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: qiyao at gcc dot gnu.org
  Target Milestone: ---

In gdb mainline (8.0.50.20171207), start gdb without executable, set a pending
breakpoint, load the executable, and run,

(gdb) b set_point1
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (set_point1) pending.
(gdb) file ./testsuite/outputs/gdb.trace/pending/pending 
Reading symbols from ./testsuite/outputs/gdb.trace/pending/pending...done.
(gdb) b main
Breakpoint 2 at 0x4007c5: file
/home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.trace/pending.c,
line 28.
(gdb) r
Starting program:
/home/yao.qi/SourceCode/gnu/build/gdb/testsuite/outputs/gdb.trace/pending/pending 
Python Exception <type 'exceptions.NameError'> Installation error:
gdb.execute_unwinders function is missing: 
Python Exception <type 'exceptions.NameError'> Installation error:
gdb.execute_unwinders function is missing: 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff63b5700 (LWP 24579)]

Thread 1 "pending" hit Breakpoint 2, Python Exception <type
'exceptions.NameError'> Installation error: gdb.execute_unwinders function is
missing: 
main () at
/home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.trace/pending.c:28
28        const char *libname = "pendshr2.sl";
(gdb) info breakpoints 
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   0xf7bd569e         <pendfunc+7>
                                ^^^^^^^^^^
2       breakpoint     keep y   0x00000000004007c5 in main 
                                                   at
/home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.trace/pending.c:28
        breakpoint already hit 1 time
(gdb) p set_point1
$1 = {<text variable, no debug info>} 0x7ffff7bd569e <pendfunc+7>

As we can see, the address of breakpoint 1 is wrong.

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