From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121933 invoked by alias); 7 Dec 2015 16:50:46 -0000 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 Received: (qmail 121923 invoked by uid 89); 7 Dec 2015 16:50:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 07 Dec 2015 16:50:45 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 4FDC8C00125F; Mon, 7 Dec 2015 16:50:44 +0000 (UTC) Received: from [10.3.113.144] (ovpn-113-144.phx2.redhat.com [10.3.113.144]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tB7GogKG005799; Mon, 7 Dec 2015 11:50:43 -0500 Subject: Re: [PATCH v3 2/2] Implement 'catch syscall' for gdbserver To: Eli Zaretskii References: <1448506425-24691-1-git-send-email-jistone@redhat.com> <1449196006-13759-1-git-send-email-jistone@redhat.com> <1449196006-13759-2-git-send-email-jistone@redhat.com> <837fkuiovv.fsf@gnu.org> <5662489B.20708@redhat.com> <83r3j1fhoq.fsf@gnu.org> Cc: gdb-patches@sourceware.org, philippe.waroquiers@skynet.be, sergiodj@redhat.com, palves@redhat.com, xdje42@gmail.com From: Josh Stone Message-ID: <5665B8E2.2080202@redhat.com> Date: Mon, 07 Dec 2015 16:50:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <83r3j1fhoq.fsf@gnu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-12/txt/msg00140.txt.bz2 On 12/05/2015 12:00 AM, Eli Zaretskii wrote: >>> Any changes since v2 in the documentation parts that require a fresh >>> review? >> >> I made the changes you requested in v2 -- v3 just has some >> merge-resolution in NEWS. But Pedro has noted some more things to >> document for the next round. > > Then I guess it's better if I review the next round, is that right? > Or do you mean this v3 _is_ that next round? The former -- I mean v4 will have a few additions. Sorry if I confused you by explicitly CCing. I just included everyone who had commented at all on prior versions, but maybe that's too greedy.