From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id U/jgFeVY2WP1biYAWB0awg (envelope-from ) for ; Tue, 31 Jan 2023 13:07:33 -0500 Received: by simark.ca (Postfix, from userid 112) id 4DDC61E128; Tue, 31 Jan 2023 13:07:33 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=MqI3YSr9; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 08B591E112 for ; Tue, 31 Jan 2023 13:07:33 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 8F9943858C36 for ; Tue, 31 Jan 2023 18:07:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9943858C36 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675188452; bh=tuhBjl1V2sCC6eum3spMIHaIpc/hRJ2/AXEZFeBiZDA=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=MqI3YSr9essK1icNKIuMf+5f6iL1ljtUxupqLzN36Ss2/oVoHjihxyD7Sypv1lkQz /xR+daLFnXdw3BdTbh/TMZOCkt0Vj79zwAeZitPdUFPGxpZKwUjPwRry5IXlHKTMR7 gZmqEn5gCyC/B7ybm9p6E3JmpgwBGizxYDaDlQ+k= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id D19AA3858D33 for ; Tue, 31 Jan 2023 18:07:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D19AA3858D33 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pMv2H-0001uF-6l; Tue, 31 Jan 2023 13:07:13 -0500 Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pMv2G-0003AL-Ka; Tue, 31 Jan 2023 13:07:12 -0500 Date: Tue, 31 Jan 2023 20:07:10 +0200 Message-Id: <83tu061stt.fsf@gnu.org> To: Andrew Burgess Cc: gdb-patches@sourceware.org In-Reply-To: <78764570698177ecf049fdab759908ca88fd7bd3.1675185990.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Tue, 31 Jan 2023 17:27:07 +0000) Subject: Re: [PATCHv3 02/13] gdb/doc: extend the documentation for conditional breakpoints References: <78764570698177ecf049fdab759908ca88fd7bd3.1675185990.git.aburgess@redhat.com> X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Cc: Andrew Burgess > Date: Tue, 31 Jan 2023 17:27:07 +0000 > From: Andrew Burgess via Gdb-patches > > +If a breakpoint condition calls a function in your program, then it is > +possible that your program could stop for some reason while in the > +called function. For example, @value{GDBN} might hit a breakpoint in > +the called function, or the called function may receive a signal > +(e.g.@ a @code{SIGSEGV}) as a result of some undefined behavior. If > +this happens then @value{GDBN} will stop. Depending on the settings > +@code{unwindonsignal} and @code{unwind-on-terminating-exception} > +(@pxref{Calling,,Calling Program Functions}) @value{GDBN} may unwind > +the stack back to the breakpoint location, or may leave the program at > +the frame where the stop occurred. This is okay, but should we perhaps tell the reader how to deal with these calamities? I presume there's something to say, otherwise why do we describe these situations? Thanks.