Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* PATCH: mention correct GCC version
@ 2004-02-18  8:46 Jim Blandy
  0 siblings, 0 replies; only message in thread
From: Jim Blandy @ 2004-02-18  8:46 UTC (permalink / raw)
  To: gdb-patches


2004-02-17  Jim Blandy  <jimb@redhat.com>

	* findvar.c (value_from_register): Doc fix.

Index: findvar.c
===================================================================
RCS file: /cvs/src/src/gdb/findvar.c,v
retrieving revision 1.72
retrieving revision 1.73
diff -c -c -F'^(' -r1.72 -r1.73
*** findvar.c	18 Feb 2004 03:12:11 -0000	1.72
--- findvar.c	18 Feb 2004 04:26:09 -0000	1.73
***************
*** 628,634 ****
  
           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
           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
--- 628,634 ----
  
           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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-02-18  8:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-18  8:46 PATCH: mention correct GCC version Jim Blandy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox