Revert the previous 7 commits of: Validate binary before use
ddc98fbf2f
Create empty nat/linux-maps.[ch] and common/target-utils.[ch]6e5b4429db
Move gdb_regex* to common/f7af1fcd75
Prepare linux_find_memory_regions_full & co. for move9904185cfd
Move linux_find_memory_regions_full & co.700ca40f6f
gdbserver build-id attribute generatorca5268b6be
Validate symbol file using build-id0a94970d66
Tests for validate symbol file using build-id gdb/ChangeLog 2015-07-15 Jan Kratochvil <jan.kratochvil@redhat.com> Revert the previous 6 commits: Create empty nat/linux-maps.[ch] and common/target-utils.[ch]. Move gdb_regex* to common/ Prepare linux_find_memory_regions_full & co. for move Move linux_find_memory_regions_full & co. gdbserver build-id attribute generator Validate symbol file using build-id gdb/gdbserver/ChangeLog 2015-07-15 Jan Kratochvil <jan.kratochvil@redhat.com> Revert the previous 3 commits: Move gdb_regex* to common/ Move linux_find_memory_regions_full & co. gdbserver build-id attribute generator gdb/doc/ChangeLog 2015-07-15 Jan Kratochvil <jan.kratochvil@redhat.com> Revert the previous 2 commits: gdbserver build-id attribute generator Validate symbol file using build-id gdb/testsuite/ChangeLog 2015-07-15 Jan Kratochvil <jan.kratochvil@redhat.com> Revert the previous commit: Tests for validate symbol file using build-id.
This commit is contained in:
parent
0a94970d66
commit
db1ff28b60
43 changed files with 830 additions and 1952 deletions
18
gdb/solist.h
18
gdb/solist.h
|
@ -75,19 +75,6 @@ struct so_list
|
|||
There may not be just one (e.g. if two segments are relocated
|
||||
differently); but this is only used for "info sharedlibrary". */
|
||||
CORE_ADDR addr_low, addr_high;
|
||||
|
||||
/* Build id decoded from .note.gnu.build-id without note header. This is
|
||||
actual BUILD_ID which comes either from the remote target via qXfer
|
||||
packet or via reading target memory. Note that if there's a
|
||||
mismatch with the associated bfd then so->abfd will be cleared.
|
||||
Reading target memory should be done by following execution view
|
||||
of the binary (following program headers in the case of ELF).
|
||||
Computing address from the linking view (following ELF section
|
||||
headers) may give incorrect build-id memory address despite the
|
||||
symbols still match.
|
||||
Such an example is a prelinked vs. unprelinked i386 ELF file. */
|
||||
size_t build_idsz;
|
||||
gdb_byte *build_id;
|
||||
};
|
||||
|
||||
struct target_so_ops
|
||||
|
@ -181,11 +168,6 @@ struct target_so_ops
|
|||
NULL, in which case no specific preprocessing is necessary
|
||||
for this target. */
|
||||
void (*handle_event) (void);
|
||||
|
||||
/* Return NULL if SO does match target SO it is supposed to
|
||||
represent. Otherwise return string describing why it does not match.
|
||||
Caller has to free the string. */
|
||||
char *(*validate) (const struct so_list *so);
|
||||
};
|
||||
|
||||
/* Free the memory associated with a (so_list *). */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue