From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24842 invoked by alias); 14 Oct 2014 18:27:40 -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 24822 invoked by uid 89); 14 Oct 2014 18:27:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout23.012.net.il Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Oct 2014 18:27:38 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0NDG004005KKTF00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Tue, 14 Oct 2014 21:27:34 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NDG004VS5XYODA0@a-mtaout23.012.net.il>; Tue, 14 Oct 2014 21:27:34 +0300 (IDT) Date: Tue, 14 Oct 2014 18:27:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] stepi/nexti: skip signal handler if "handle nostop" signal arrives In-reply-to: <1413308910-30423-1-git-send-email-palves@redhat.com> To: Pedro Alves Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ppdu5wx7.fsf@gnu.org> References: <1413308910-30423-1-git-send-email-palves@redhat.com> X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00356.txt.bz2 > From: Pedro Alves > Date: Tue, 14 Oct 2014 18:48:30 +0100 > > --- a/gdb/doc/gdb.texinfo > +++ b/gdb/doc/gdb.texinfo > @@ -5526,6 +5526,11 @@ Their full names are: > @value{GDBN} should not stop your program when this signal happens. It may > still print a message telling you that the signal has come in. > > +If this signal arrives while a stepping command (e.g., @code{step}) is > +in progress, the signal's handler is skipped (though still executed if > +@code{pass} is in effect; see below). @value{GDBN} will still stop > +your program if the handler hits a breakpoint. This description is confusing. For starters, it only mentions some of the possible setting of signal handling, and keeps silence about the rest. Either we should describe what happens with all of them, one by one, or (better) says something that will explain how we handle them all, at once. Also, I believe the description of stepping should mention this aspect, with a cross-reference to here. > +If a stepping command is issued after the program stops for a signal, > +and @code{pass} is in effect for that signal, @value{GDBN} steps into > +the signal's handler (if the target supports it). Again, this left me wondering. E.g., if the program stops for a signal, then we are already in the signal handler, no? So the fact that stepping commands continue there is a no-brainer, right? Or a I again confused? Thanks.