Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: COMMIT: addrmap changes
Date: Wed, 05 Dec 2007 21:34:00 -0000	[thread overview]
Message-ID: <m37ijsq13t.fsf@codesourcery.com> (raw)
In-Reply-To: <20071205014127.GA12545@caradoc.them.org> (Daniel Jacobowitz's message of "Tue, 4 Dec 2007 20:41:27 -0500")


Daniel Jacobowitz <drow at false.org> writes:
> On Tue, Dec 04, 2007 at 03:44:27PM -0800, Jim Blandy wrote:
>> 
>> I've committed the following, approved in another thread.
>
> Thanks.  Could you please, please write a NEWS entry for this?

Sure.  Is the below okay?

I thought it would be nice to consolidate this with the multi-location
breakpoint announcement under a "debugging optimized code" category,
but the breakpoint work is also a C++ issue.

gdb/ChangeLog:
2007-12-05  Jim Blandy  <jimb@codesourcery.com>

	* NEWS: Mention support for non-contiguous lexical blocks and
	function bodies.

diff -r 55dcfe0668ab gdb/NEWS
--- a/gdb/NEWS	Wed Dec 05 10:18:35 2007 -0800
+++ b/gdb/NEWS	Wed Dec 05 13:29:46 2007 -0800
@@ -19,6 +19,10 @@ is resolved.
 * GDB now supports breakpoints with multiple locations,
 including breakpoints on C++ constructors, inside C++ templates,
 and in inlined functions.
+
+* GDB's ability to debug optimized code has been improved.  GDB more
+accurately identifies function bodies and lexical blocks that occupy
+more than one contiguous range of addresses.
 
 * Target descriptions can now describe registers for PowerPC.
 


  reply	other threads:[~2007-12-05 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 23:44 Jim Blandy
2007-12-05  1:41 ` Daniel Jacobowitz
2007-12-05 21:34   ` Jim Blandy [this message]
2007-12-06  4:35     ` Eli Zaretskii
2007-12-06 17:26       ` Jim Blandy
2007-12-05 22:55 ` Pedro Alves
2007-12-06 21:41   ` Jim Blandy

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=m37ijsq13t.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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