summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2004-02-18 04:26:09 +0000
committerJim Blandy <jimb@codesourcery.com>2004-02-18 04:26:09 +0000
commitfd72d48dc3073b8a60c3d713fcff53e67c2205c8 (patch)
tree99cb078ffa471bfe48e335ee0bbfe6b455632503
parent80a6cb61729457702bfd4219670dfe67abf53d21 (diff)
downloadgdb-fd72d48dc3073b8a60c3d713fcff53e67c2205c8.tar.gz
* findvar.c (value_from_register): Doc fix.
-rw-r--r--gdb/ChangeLog4
-rw-r--r--gdb/findvar.c2
2 files changed, 5 insertions, 1 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index df32cf3ee36..158cfa5dc74 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2004-02-17 Jim Blandy <jimb@redhat.com>
+
+ * findvar.c (value_from_register): Doc fix.
+
2004-02-17 Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Committed by Jim Blandy <jimb@redhat.com>.
diff --git a/gdb/findvar.c b/gdb/findvar.c
index 157a2db8420..3cb40b2c871 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