darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* findvar.c (value_from_register): Doc fix.

Browse source
This commit is contained in:
Jim Blandy 2004-02-19 22:45:31 +00:00
parent 95051d277e
commit f98c22d517
2 changed files with 12 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/ChangeLog
View file

@ -1,3 +1,7 @@
2004-02-19 Jim Blandy <jimb@redhat.com>
* findvar.c (value_from_register): Doc fix.
2004-02-19 Jeff Johnston <jjohnstn@redhat.com>
* printcmd.c (print_scalar_formatted): Do not check for sizeof

16
gdb/findvar.c
View file

@ -627,14 +627,14 @@ value_from_register (struct type *type, int regnum, struct frame_info *frame)
error.
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.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
actually the only known way to get a zero-length value
allocated to a register --- which is what it takes to make it
here.)
like 'struct {}' (a GCC extension, not valid ISO C). GDB may
also create them when it finds 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 actually the only known way to get a
zero-length value allocated to a register --- which is what
it takes to make it here.)
We'll just attribute the value to the original register. */
VALUE_LVAL (v) = lval_register;