From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: mention correct GCC version
Date: Wed, 18 Feb 2004 08:46:00 -0000 [thread overview]
Message-ID: <vt2znbgpyij.fsf@zenia.home> (raw)
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
reply other threads:[~2004-02-18 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vt2znbgpyij.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox