diff options
| author | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-04-22 04:05:51 +0000 |
|---|---|---|
| committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-04-22 04:05:51 +0000 |
| commit | fc312cc6f989577efea43ad1ea3f5fc75054e5a6 (patch) | |
| tree | 96615dcfd9547cbeba979215bae5e9ad0b855f4f /gdb/coffread.c | |
| parent | 98ef6f318811424f774af31d52f171b2eecfe48c (diff) | |
| download | gdb-fc312cc6f989577efea43ad1ea3f5fc75054e5a6.zip gdb-fc312cc6f989577efea43ad1ea3f5fc75054e5a6.tar.gz gdb-fc312cc6f989577efea43ad1ea3f5fc75054e5a6.tar.bz2 | |
revise comment for last change
Diffstat (limited to 'gdb/coffread.c')
| -rw-r--r-- | gdb/coffread.c | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/gdb/coffread.c b/gdb/coffread.c index 4a8231b..d4e6db8 100644 --- a/gdb/coffread.c +++ b/gdb/coffread.c @@ -915,8 +915,19 @@ read_coff_symtab (symtab_offset, nsyms, objfile) perror_with_name(objfile->name); /* Work around a stdio bug in SunOS4.1.1 (this makes me nervous.... - it's hard to know I've really worked around it. This should be - harmless, anyway). */ + it's hard to know I've really worked around it. The fix should be + harmless, anyway). The symptom of the bug is that the first + fread (in read_one_sym), will (in my example) actually get data + from file offset 268, when the fseek was to 264 (and ftell shows + 264). This causes all hell to break loose. I was unable to + reproduce this on a short test program which operated on the same + file, performing (I think) the same sequence of operations. + + It stopped happening when I put in this rewind(). + + FIXME: Find out if this has been reported to Sun, whether it has + been fixed in a later release, etc. */ + rewind (stream); /* Position to read the symbol table. */ |