From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id sEb/LFMWyWNTMxoAWB0awg (envelope-from ) for ; Thu, 19 Jan 2023 05:07:15 -0500 Received: by simark.ca (Postfix, from userid 112) id AE3C91E128; Thu, 19 Jan 2023 05:07:15 -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=yybgyRk/; 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=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.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 6ABE61E0D3 for ; Thu, 19 Jan 2023 05:07:15 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 0BBA33858288 for ; Thu, 19 Jan 2023 10:07:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0BBA33858288 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674122834; bh=cJbXwoeG0o1wR0mZcRY0jmF+EdkhDwsV8yam3KVigHM=; 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=yybgyRk/ASh99Nklkj2mOoyilf+60Kgimub1tRRL/eKNJde2q3g+hq0H4gotLMKYm FWP+apcGHuCewbNszIyeS9+SX/LZzIck8XbmSpA2iOT/Jorz3adczvLLs5LlYoYo1h b0jnlfzFr4UH8wruw0a/8tG1Gm/piIIfZ1P9g5/0= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id BB9743858C52 for ; Thu, 19 Jan 2023 10:06:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BB9743858C52 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 1pIRor-0005Sz-IY; Thu, 19 Jan 2023 05:06:53 -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 1pIRon-0002Xz-MK; Thu, 19 Jan 2023 05:06:53 -0500 Date: Thu, 19 Jan 2023 12:07:06 +0200 Message-Id: <83o7quzvlh.fsf@gnu.org> To: "Aktemur, Tankut Baris" Cc: aburgess@redhat.com, gdb-patches@sourceware.org In-Reply-To: (gdb-patches@sourceware.org) Subject: Re: [PATCHv2 02/13] gdb/doc: extend the documentation for conditional breakpoints References: <93c3968f10fcc7e2c85e1dae3cbbf1bcf122ea44.1674058359.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" > Date: Thu, 19 Jan 2023 09:04:03 +0000 > From: "Aktemur, Tankut Baris 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 behaviour, if > > It seems to me like this could be "... behaviour. If ...". And in any case it should be "behavior", as we use US English spelling.