diff options
| author | Jim Blandy <jimb@codesourcery.com> | 2004-02-18 04:26:09 +0000 |
|---|---|---|
| committer | Jim Blandy <jimb@codesourcery.com> | 2004-02-18 04:26:09 +0000 |
| commit | 05957fdb1caa49bf59938131d51f31174b5d2c44 (patch) | |
| tree | 2a2c23c1349b03ca478385eb458ab5486dc9ad8b /gdb/findvar.c | |
| parent | c253954e00ea3c23f7ff74f73b94c85ce135b82e (diff) | |
| download | fsf-binutils-gdb-05957fdb1caa49bf59938131d51f31174b5d2c44.zip fsf-binutils-gdb-05957fdb1caa49bf59938131d51f31174b5d2c44.tar.gz fsf-binutils-gdb-05957fdb1caa49bf59938131d51f31174b5d2c44.tar.bz2 | |
* findvar.c (value_from_register): Doc fix.
Diffstat (limited to 'gdb/findvar.c')
| -rw-r--r-- | gdb/findvar.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/findvar.c b/gdb/findvar.c index 157a2db..3cb40b2 100644 --- a/gdb/findvar.c +++ b/gdb/findvar.c @@ -628,7 +628,7 @@ value_from_register (struct type *type, int regnum, struct frame_info *frame) Zero-length types can legitimately arise from declarations like 'struct {}'. GDB may also create them when it finds - bogus debugging information; for example, in GCC 2.94.4 and + bogus debugging information; for example, in GCC 2.95.4 and binutils 2.11.93.0.2, the STABS BINCL->EXCL compression process can create bad type numbers. GDB reads these as TYPE_CODE_UNDEF types, with zero length. (That bug is |