From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6699 invoked by alias); 19 Aug 2010 03:03:42 -0000 Received: (qmail 6491 invoked by uid 22791); 19 Aug 2010 03:03:41 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 19 Aug 2010 03:03:34 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0L7D00L00PKMQE00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Thu, 19 Aug 2010 06:02:36 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.220.100]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L7D00LINPSBM750@a-mtaout20.012.net.il>; Thu, 19 Aug 2010 06:02:36 +0300 (IDT) Date: Thu, 19 Aug 2010 03:03:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] More NEWS for 7.2 In-reply-to: <4C6C8E1F.1010104@codesourcery.com> To: Stan Shebs Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838w43qpbd.fsf@gnu.org> References: <4C6C8E1F.1010104@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-08/txt/msg00326.txt.bz2 > Date: Wed, 18 Aug 2010 18:51:27 -0700 > From: Stan Shebs > > 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 > > * 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?