diff options
| author | Steve Chamberlain <sac@cygnus> | 1992-10-08 16:02:09 +0000 |
|---|---|---|
| committer | Steve Chamberlain <sac@cygnus> | 1992-10-08 16:02:09 +0000 |
| commit | 294eaca479e9ced9a87b958c37feb2c570aa1595 (patch) | |
| tree | bb7a6bb0ac1df535df9c7fe230c1a0bc81b85ab3 /bfd/elf.c | |
| parent | 0da7012441eaccf157dc44c8cc110fbf2d3f8376 (diff) | |
| download | gdb-294eaca479e9ced9a87b958c37feb2c570aa1595.zip gdb-294eaca479e9ced9a87b958c37feb2c570aa1595.tar.gz gdb-294eaca479e9ced9a87b958c37feb2c570aa1595.tar.bz2 | |
Some of these are guesses, if you know different, just yell.
Thu Oct 8 08:52:48 1992 Steve Chamberlain (sac@thepub.cygnus.com)
Now a bfd knows whether underscores are normally prepended
to symbols in its file format. Helps with error messages.
* aout-adobe.c, aout-target.h, bout.c, coff-a29k.c, coff-h8300.c,
coff-z8k.c: targets set so they have leading underscore
* coff-i386.c, coff-i960.c, coff-m68k.c, coff-mips.c, coff-m88k.c,
coff-rs6000.c, coff-we32k.c, elf.c, ieee.c, srec.c: targets set
without leading underscore flag
* targets.c: add symbol leading char to xvec description
* bfd-in.h (bfd_get_symbol_leading_char): new macro.
Diffstat (limited to 'bfd/elf.c')
| -rw-r--r-- | bfd/elf.c | 11 |
1 files changed, 10 insertions, 1 deletions
@@ -781,7 +781,7 @@ DEFUN(bfd_prpsinfo,(abfd, descdata, descsz, filepos), { if ((core_prpsinfo (abfd) = bfd_alloc (abfd, descsz)) != NULL) { - bcopy (descdata, core_prpsinfo (abfd), descsz); + memcpy (core_prpsinfo (abfd), descdata, descsz); } } } @@ -2484,6 +2484,11 @@ bfd_target elf_big_vec = (SEC_HAS_CONTENTS | SEC_ALLOC | SEC_LOAD | SEC_RELOC | SEC_READONLY | SEC_CODE | SEC_DATA), + + /* leading_symbol_char: is the first char of a user symbol + predictable, and if so what is it */ + 0, + /* ar_pad_char: pad character for filenames within an archive header FIXME: this really has nothing to do with ELF, this is a characteristic of the archiver and/or os and should be independently tunable */ @@ -2556,6 +2561,10 @@ bfd_target elf_little_vec = (SEC_HAS_CONTENTS | SEC_ALLOC | SEC_LOAD | SEC_RELOC | SEC_READONLY | SEC_DATA), + /* leading_symbol_char: is the first char of a user symbol + predictable, and if so what is it */ + 0, + /* ar_pad_char: pad character for filenames within an archive header FIXME: this really has nothing to do with ELF, this is a characteristic of the archiver and/or os and should be independently tunable */ |