From 05957fdb1caa49bf59938131d51f31174b5d2c44 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Wed, 18 Feb 2004 04:26:09 +0000 Subject: [PATCH] * findvar.c (value_from_register): Doc fix. --- gdb/ChangeLog | 4 ++++ gdb/findvar.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) 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 + + * findvar.c (value_from_register): Doc fix. + 2004-02-17 Ulrich Weigand Committed by Jim Blandy . 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 -- 2.30.2