diff options
Diffstat (limited to 'gnu/usr.bin/binutils/gdb/objfiles.h')
| -rw-r--r-- | gnu/usr.bin/binutils/gdb/objfiles.h | 33 |
1 files changed, 3 insertions, 30 deletions
diff --git a/gnu/usr.bin/binutils/gdb/objfiles.h b/gnu/usr.bin/binutils/gdb/objfiles.h index 2b8ca7d350f..afbe8d26d38 100644 --- a/gnu/usr.bin/binutils/gdb/objfiles.h +++ b/gnu/usr.bin/binutils/gdb/objfiles.h @@ -44,9 +44,8 @@ struct objfile_data; to the user executable's recorded entry point, as if the call had been made directly by the kernel. - The traditional gdb method of using this info is to use the - recorded entry point to set the variables - deprecated_entry_file_lowpc and deprecated_entry_file_highpc from + The traditional gdb method of using this info was to use the + recorded entry point to set the entry-file's lowpc and highpc from the debugging information, where these values are the starting address (inclusive) and ending address (exclusive) of the instruction space in the executable which correspond to the @@ -57,7 +56,7 @@ struct objfile_data; NOTE: cagney/2003-09-09: It turns out that this "traditional" method doesn't work. Corinna writes: ``It turns out that the call - to deprecated_inside_entry_file destroys a meaningful backtrace + to test for "inside entry file" destroys a meaningful backtrace under some conditions. E. g. the backtrace tests in the asm-source testcase are broken for some targets. In this test the functions are all implemented as part of one file and the testcase is not @@ -111,32 +110,6 @@ struct entry_info #define INVALID_ENTRY_POINT (~0) /* ~0 will not be in any file, we hope. */ - /* Start (inclusive) and end (exclusive) of function containing the - entry point. */ - - CORE_ADDR entry_func_lowpc; - CORE_ADDR entry_func_highpc; - - /* Start (inclusive) and end (exclusive) of object file containing the - entry point. */ - - CORE_ADDR deprecated_entry_file_lowpc; - CORE_ADDR deprecated_entry_file_highpc; - - /* Start (inclusive) and end (exclusive) of the user code main() function. */ - - CORE_ADDR main_func_lowpc; - CORE_ADDR main_func_highpc; - -/* Use these values when any of the above ranges is invalid. */ - -/* We use these values because it guarantees that there is no number that is - both >= LOWPC && < HIGHPC. It is also highly unlikely that 3 is a valid - module or function start address (as opposed to 0). */ - -#define INVALID_ENTRY_LOWPC (3) -#define INVALID_ENTRY_HIGHPC (1) - }; /* Sections in an objfile. |