From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: NEWS entries for 6.1.1 dwarf changes?
Date: Fri, 11 Jun 2004 14:21:00 -0000 [thread overview]
Message-ID: <200406111421.i5BELAr1001522@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40C9363B.5040108@gnu.org> (message from Andrew Cagney on Fri, 11 Jun 2004 00:34:03 -0400)
Date: Fri, 11 Jun 2004 00:34:03 -0400
From: Andrew Cagney <cagney@gnu.org>
Hello,
These 6.1.1 changes need a NEWS entry, anyone?
2004-05-01 Mark Kettenis <kettenis@gnu.org>
* dwarf2-frame.c (read_encoded_value): Handle DW_EH_PE_funcrel
encondings. Fixes PR gdb/1628.
Andrew
Would that be really useful? This stuff is mentioned in the
ChangeLog. Oh well, I don't want to hold up the release, so here's
some blurb about the change shown above.
Committed to the branch,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* NEWS: Mention fix for PR gdb/1628.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.138.2.5
diff -u -p -r1.138.2.5 NEWS
--- NEWS 4 Jun 2004 17:03:25 -0000 1.138.2.5
+++ NEWS 11 Jun 2004 14:16:00 -0000
@@ -19,6 +19,11 @@ systems (Solaris, IRIX). Ref: server/51
Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
has been updated to use constant array sizes.
+* Bug fixes
+
+gdb/1628: GDB now handles the DW_EH_PE_funcrel encoding in DWARF Call
+Frame Info.
+
*** Changes in GDB 6.1:
* Removed --with-mmalloc
next prev parent reply other threads:[~2004-06-11 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 4:34 Andrew Cagney
2004-06-11 14:21 ` Mark Kettenis [this message]
2004-06-11 15:17 ` Andrew Cagney
2004-06-11 15:18 ` Andrew Cagney
2004-06-11 17:07 ` 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=200406111421.i5BELAr1001522@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@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