This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[patch] Require CALL_DUMMY_LOCATIONS initialization
- To: gdb-patches at sources dot redhat dot com
- Subject: [patch] Require CALL_DUMMY_LOCATIONS initialization
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 06 Nov 2001 14:57:29 -0500
Hello,
It turns out that a multi-arch GDB can't do much unless
CALL_DUMMY_LOCATIONS is initialized.
The attached tweeks things so that a multi-arch target must provide a
value for CALL_DUMMY_LOCATIONS. If it doesn't then it gets an internal
error.
I've checked it in.
enjoy,
Andrew
2001-11-06 Andrew Cagney <ac131313@redhat.com>
* gdbarch.sh (CALL_DUMMY_LOCATION): Require a value.
* gdbarch.c: Regenerate.
Index: gdbarch.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.sh,v
retrieving revision 1.88
diff -p -r1.88 gdbarch.sh
*** gdbarch.sh 2001/11/06 18:06:00 1.88
--- gdbarch.sh 2001/11/06 19:24:15
*************** f:2:CANNOT_FETCH_REGISTER:int:cannot_fet
*** 437,443 ****
f:2:CANNOT_STORE_REGISTER:int:cannot_store_register:int regnum:regnum:::cannot_register_not::0
#
v:1:USE_GENERIC_DUMMY_FRAMES:int:use_generic_dummy_frames::::0:-1
! v:2:CALL_DUMMY_LOCATION:int:call_dummy_location::::0:0
f:2:CALL_DUMMY_ADDRESS:CORE_ADDR:call_dummy_address:void:::0:0::gdbarch->call_dummy_location == AT_ENTRY_POINT && gdbarch->call_dummy_address == 0
v:2:CALL_DUMMY_START_OFFSET:CORE_ADDR:call_dummy_start_offset::::0:-1:::0x%08lx
v:2:CALL_DUMMY_BREAKPOINT_OFFSET:CORE_ADDR:call_dummy_breakpoint_offset::::0:-1::gdbarch->call_dummy_breakpoint_offset_p && gdbarch->call_dummy_breakpoint_offset == -1:0x%08lx::CALL_DUMMY_BREAKPOINT_OFFSET_P
--- 437,443 ----
f:2:CANNOT_STORE_REGISTER:int:cannot_store_register:int regnum:regnum:::cannot_register_not::0
#
v:1:USE_GENERIC_DUMMY_FRAMES:int:use_generic_dummy_frames::::0:-1
! v:1:CALL_DUMMY_LOCATION:int:call_dummy_location::::0:0
f:2:CALL_DUMMY_ADDRESS:CORE_ADDR:call_dummy_address:void:::0:0::gdbarch->call_dummy_location == AT_ENTRY_POINT && gdbarch->call_dummy_address == 0
v:2:CALL_DUMMY_START_OFFSET:CORE_ADDR:call_dummy_start_offset::::0:-1:::0x%08lx
v:2:CALL_DUMMY_BREAKPOINT_OFFSET:CORE_ADDR:call_dummy_breakpoint_offset::::0:-1::gdbarch->call_dummy_breakpoint_offset_p && gdbarch->call_dummy_breakpoint_offset == -1:0x%08lx::CALL_DUMMY_BREAKPOINT_OFFSET_P