Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: eliz@gnu.org, dan@debian.org
Cc: gdb-patches@sources.redhat.com
Subject: [rfc/NEWS] GDB works with GCC -feliminate-dwarf2-dups.
Date: Sun, 17 Oct 2004 18:12:00 -0000	[thread overview]
Message-ID: <4172B5F4.nailMEV1154GO@mindspring.com> (raw)

This looks like NEWS to me.

Daniel, did I get the details right?

Eli, is this okay?

===

2004-10-17  Michael Chastain  <mec.gnu@mindspring.com>

	* NEWS: GDB works with GCC -feliminate-dwarf2-dups.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.161
diff -c -3 -p -r1.161 NEWS
*** NEWS	12 Aug 2004 21:44:19 -0000	1.161
--- NEWS	17 Oct 2004 18:07:34 -0000
***************
*** 1,7 ****
  		What has changed in GDB?
  	     (Organized release by release)
  
! *** Changes since GDB 6.2:
  
  *** Changes in GDB 6.2.1:
  
--- 1,12 ----
  		What has changed in GDB?
  	     (Organized release by release)
  
! *** Changes since GDB 6.2.1:
! 
! * GDB works with GCC -feliminate-dwarf2-dups
! 
! GDB now works with programs compiled with -feliminate-dwarf2-dups.
! You must use GCC 3.3.4 or later to use this option.
  
  *** Changes in GDB 6.2.1:
  


             reply	other threads:[~2004-10-17 18:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 18:12 Michael Chastain [this message]
2004-10-17 18:31 ` Daniel Jacobowitz
2004-10-17 18:53   ` Michael Chastain
2004-10-17 19:13     ` Daniel Jacobowitz
2004-10-17 20:11       ` Michael Chastain
2004-10-18  5:01         ` Eli Zaretskii
2004-10-18 20:14           ` Michael Chastain
2004-10-19  4:39             ` Eli Zaretskii
2004-10-19 13:23               ` Daniel Jacobowitz
2004-10-19 20:05                 ` Eli Zaretskii
2004-10-19 19:37               ` Michael Chastain
2004-10-17 19:45   ` Eli Zaretskii
2004-10-17 19:42 ` Eli Zaretskii

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=4172B5F4.nailMEV1154GO@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=dan@debian.org \
    --cc=eliz@gnu.org \
    --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