From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Target memory overhaul
Date: Wed, 16 Aug 2006 18:32:00 -0000 [thread overview]
Message-ID: <20060816141034.GA21971@nevyn.them.org> (raw)
In-Reply-To: <uk659l6ac.fsf@gnu.org>
On Wed, Aug 16, 2006 at 06:15:55AM +0300, Eli Zaretskii wrote:
> > Date: Tue, 15 Aug 2006 15:58:10 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > > > That was broken for a while (at least since 6.1, maybe 6.0) and is now
> > > > fixed; Eli, is that NEWS-worthy?
> > >
> > > What is the user-visible change in behavior?
> >
> > `set trust-readonly-sections on' (documented) used to be ignored;
> > suddenly it is honored again.
>
> Then I agree that we should mention it in NEWS.
This OK? I double checked the broken versions - good thing, since I
was wrong.
2006-08-16 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention "set trust-readonly-sections" fix.
---
gdb/NEWS | 3 +++
1 file changed, 3 insertions(+)
Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS 2006-08-16 10:03:16.000000000 -0400
+++ src/gdb/NEWS 2006-08-16 10:09:53.000000000 -0400
@@ -11,6 +11,9 @@ running on a Windows system over TCP/IP
Cygwin debugging. Both single-threaded and multi-threaded programs are
supported.
+* The "set trust-readonly-sections" command works again. This command was
+broken in GDB 6.3, 6.4, and 6.5.
+
* New commands
set substitute-path
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-16 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 5:28 Daniel Jacobowitz
2006-08-15 19:30 ` Daniel Jacobowitz
2006-08-16 3:16 ` Eli Zaretskii
2006-08-16 8:15 ` Daniel Jacobowitz
2006-08-16 14:10 ` Eli Zaretskii
2006-08-16 18:32 ` Daniel Jacobowitz [this message]
2006-08-17 2:14 ` Eli Zaretskii
2006-08-17 9:12 ` Daniel Jacobowitz
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=20060816141034.GA21971@nevyn.them.org \
--to=drow@false.org \
--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