[Bug ada/25811] [ada] start attempts to set breakpoint on main of previous exec

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
The bug here is that ada_main_name reads memory to find
the name:

      main_program_name = target_read_string (main_program_name_addr, 1024);

The symbol is correctly found in the new executable:

(top-gdb) p msym.objfile.original_name
$19 = 0x3424020
"/home/tromey/gdb/build/gdb/testsuite/outputs/gdb.ada/exec_changed/./common"

... but the memory comes from the running inferior.

If I "kill" the inferior first, it works:

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 2209503) killed]
(gdb) file ./common 
Load new symbol table from "./common"? (y or n) y
Reading symbols from ./common...
(gdb) info main
_ada_second


I'm not really sure what we want to do about this case.

Another way to make it work is "set trust-readonly-sections on".
Perhaps ada_main_name could do this temporarily.  I can't tell
if I think that would be a hack or not.  Actually... instead of
modifying the flag, it might be better to just dig through
the BFD section data by hand.  (Not sure.)

A better solution would be to modify the compiler to emit
DW_AT_main_subprogram, but I am not sure how hard that would be.

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