* findvar.c (value_from_register): Doc fix.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index df32cf3ee366053d9335f571c808cd33856d08ad..158cfa5dc743211af5e4ede0be6a7f4f00b1c4a9 100644 (file)
--- 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 157a2db84206d3b86ab8948616503077978c4a04..3cb40b2c8713eb6918bcd708e839f0eb7318ccff 100644 (file)
--- 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