diff options
| author | Kazu Hirata <kazu@codesourcery.com> | 2003-11-30 18:40:41 +0000 |
|---|---|---|
| committer | Kazu Hirata <kazu@codesourcery.com> | 2003-11-30 18:40:41 +0000 |
| commit | ca5fd743473b81a0d15fafe4e39a997ca6ca27f9 (patch) | |
| tree | 1340d16e0f436d0d3e4049cdba9456898e455bfb /bfd/ecofflink.c | |
| parent | 40cd81ac42061e72eb93a0d402b6352c3d9a5dd5 (diff) | |
| download | binutils-redhat-ca5fd743473b81a0d15fafe4e39a997ca6ca27f9.tar.gz | |
* ChangeLog: Fix typos.
* ecoff.c: Fix comment typos.
* ecofflink.c: Likewise.
* format.c: Likewise.
* hp300hpux.c: Likewise.
* i386linux.c: Likewise.
* ieee.c: Likewise.
* m68klinux.c: Likewise.
* mach-o.h: Likewise.
* mipsbsd.c: Likewise.
* oasys.c: Likewise.
* opncls.c: Likewise.
* peXXigen.c: Likewise.
* reloc.c: Likewise.
* reloc16.c: Likewise.
* section.c: Likewise.
* simple.c: Likewise.
* som.c: Likewise.
* som.h: Likewise.
* sparclinux.c: Likewise.
* srec.c: Likewise.
* syms.c: Likewise.
* targets.c: Likewise.
* tekhex.c: Likewise.
* versados.c: Likewise.
* vms-gsd.c: Likewise.
* vms-hdr.c: Likewise.
* vms-misc.c: Likewise.
* xcofflink.c: Likewise.
* xsym.h: Likewise.
* bfd-in2.h: Regenerate.
Diffstat (limited to 'bfd/ecofflink.c')
| -rw-r--r-- | bfd/ecofflink.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bfd/ecofflink.c b/bfd/ecofflink.c index 89edae344f..9e23848fda 100644 --- a/bfd/ecofflink.c +++ b/bfd/ecofflink.c @@ -2007,7 +2007,7 @@ lookup_line (abfd, debug_info, debug_swap, line_info) /* eraxxon: 'fdrtab_lookup' doesn't give what we want, at least for Compaq's C++ compiler 6.2. Consider three FDRs with starting addresses of x, y, and z, respectively, such that x < y < z. Assume further that - y < 'offset' < z. It is possble at times that the PDR for 'offset' is + y < 'offset' < z. It is possible at times that the PDR for 'offset' is associated with FDR x and *not* with FDR y. Erg!! From a binary dump of my C++ test case 'moo' using Compaq's coffobjanl @@ -2030,7 +2030,7 @@ lookup_line (abfd, debug_info, debug_swap, line_info) Since the FDRs that are causing so much havok (in this case) 1) do not describe actual files (fdr.rss == -1), and 2) contain only compiler - genarated routines, I thought a simple fix would be to exclude them from + generated routines, I thought a simple fix would be to exclude them from the FDR table in 'mk_fdrtab'. But, besides not knowing for certain whether this would be correct, it creates an additional problem. If we happen to ask for source file info on a compiler generated (procedure) |