From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] More NEWS for 7.2
Date: Thu, 19 Aug 2010 03:03:00 -0000 [thread overview]
Message-ID: <838w43qpbd.fsf@gnu.org> (raw)
In-Reply-To: <4C6C8E1F.1010104@codesourcery.com>
> Date: Wed, 18 Aug 2010 18:51:27 -0700
> From: Stan Shebs <stan@codesourcery.com>
>
> This patch adds notes for overlooked user-visible changes in 7.2. The
> diff is for the 7.2 branch, but I'll paste into trunk as well, once any
> wording glitches have been sorted out. Please don't make me define all
> the terms. :-)
>
> Stan
>
> 2010-08-18 Stan Shebs <stan@codesourcery.com>
>
> * NEWS: Mention some additional changes.
Thanks. I have only one request:
> + set may-write-registers on|off
> + set may-write-memory on|off
> + set may-insert-breakpoints on|off
> + set may-insert-tracepoints on|off
> + set may-insert-fast-tracepoints on|off
> + set may-interrupt on|off
> + Set individual permissions for different kinds of GDB effects on the
> + target. Note that some of these settings can have undesirable or
> + surprising consequences.
Can we add a sentence saying what happens with disallowed operations?
Do they fail (silently or vociferously)? do they crash GDB? something
else?
prev parent reply other threads:[~2010-08-19 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 1:51 Stan Shebs
2010-08-19 3:03 ` Eli Zaretskii [this message]
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=838w43qpbd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).