From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2610:1c1:1:606c::19:2]) by sourceware.org (Postfix) with ESMTPS id 06F743858D20 for ; Wed, 31 May 2023 15:58:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 06F743858D20 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=FreeBSD.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "mx1.freebsd.org", Issuer "R3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id 4QWYnc6tvgz3LNQ; Wed, 31 May 2023 15:57:56 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWYnc60cxz4StC; Wed, 31 May 2023 15:57:56 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685548676; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ildmtYcL8nPXT3pPYnzz/ezuTAEggKC4JvTQzf+zF0Y=; b=OWjpdVuz1/0X9CQMTw19y4+Lpp4bo+pWaYbgMoJT0ZnlvzH3fh3xyf0nUduRFCKGCAfUj9 xY8dFTecsUNhXD4aXpY1ifW8my1vLECqUDZ8MQpi3t9ZS1W6jAw/3azowIo9fgzgdsbvMF OKxpz9QUTUHNdqBeB323RrlqZZ+zimPm6R3gPdeuSKRsu1U9YOvfnGYhQaktspWlYjXIUx wvmHKgweo9/yoCNyZyN6hgRlkaeM5cvpVQaMHP1w7pOfUbJuYbr+CMDD9Kq2Qze9WHPAUT lyUUEXGu77nW/xG0NHCGVWWx6QnhYfEn5u86VutRo2vmS9yActjr/bpEJTTisw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685548676; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ildmtYcL8nPXT3pPYnzz/ezuTAEggKC4JvTQzf+zF0Y=; b=CjF7oER49bVChFHnEyjc3od6yIqGKa94PuB8AGaPtZyKDqzPN9mg4EUpKg+/Ph8t845bJX z5fXA+IzbrXFYPVLmpMQw5kvDXoCPaESIfU/0SDcL5v74SqYfCkIjGrE++m+bBeiCPyIMM s3hXbTs8Y3hN9+M+366E2LgcvJwRKjulfjdhKcLKA+WtWu6A5PGZ4dGkOV2wsvoc6oSkZm hjm2gvw6ERrOOX1a9ImIY9oUAIdZOuVMYzzIP4kUDF5pQ0rDWghwPr/2nzMoUemTrbKj5a 2rmTSJQRKFQh9fnlI5lZr0N0fcZbU4yC1zWcDg46cnUmZxF8J8X2OcKFOfSmgg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685548676; a=rsa-sha256; cv=none; b=jJnaTA4f15wvzTBrF+/YXRnsIsmllaBL6cIdYkIsfQ/IGE8UCFANBMW0Gs1z6ivvnwpvb9 nqSmlvK6KhC7n30gAMt2n7mLkK1fF8KLoIelB2bq1O78wN8r/CpNrnbYMZkyqlEMJjEFmd W+BnhGiWtfb5KjIWKOEH9TeFgSdqO86EgNjWX6oPUp7aD3aSasPD+W6NKNTPMaEbGJlp4l NrbNkTpebyv3DsvnkgE3mgfMZFvzO5Vn5KTyVhAEKhv6w/+cSBeXGFpq57Fh0xZ2qugVw6 /joG414ogHMNb/gyBk51rFKMhOzAemsJPTFY4uqJLfKVItfnJ3x3Gxz6yPEVVw== Received: from [IPV6:2601:648:8680:16b0:41d7:c274:c720:71a2] (unknown [IPv6:2601:648:8680:16b0:41d7:c274:c720:71a2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QWYnZ59zxz1BS4; Wed, 31 May 2023 15:57:54 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: <95c62feb-4189-64a8-c819-b5d0717b7734@FreeBSD.org> Date: Wed, 31 May 2023 08:57:52 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Why are these two methods default_memory_insert_breakpoint() and default_memory_remove_breakpoint() called multiple times Content-Language: en-US To: hilbert , gdb@sourceware.org References: <3141f115.df17.18871148f89.Coremail.swdtian@163.com> From: John Baldwin In-Reply-To: <3141f115.df17.18871148f89.Coremail.swdtian@163.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 5/31/23 2:12 AM, hilbert via Gdb wrote: > Hi, > > I just inserted a breakpoint, shouldn't the two methods default_memory_insert_breakpoint() and default_memory_remove_breakpoint() be used only once? > > There is only one breakpoint, why both functions default_memory_insert_breakpoint() and default_memory_remove_breakpoint() are called before stopping and after stopping (after the continue command), why? GDB inserts some of its own internal breakpoints. For example, in the runtime linker/loader there is a special symbol GDB sets a breakpoint on so it can be notified about shared libraries being loaded or unloaded. If you are using libthread_db on a target it may install internal breakpoints to detect thread creation and thread exit as well. -- John Baldwin