From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 3B7eKh1r72JZLCIAWB0awg (envelope-from ) for ; Sun, 07 Aug 2022 03:34:53 -0400 Received: by simark.ca (Postfix, from userid 112) id A2DB51EA05; Sun, 7 Aug 2022 03:34:53 -0400 (EDT) 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=ApJFTMk1; 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=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,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 56FC31E745 for ; Sun, 7 Aug 2022 03:34:53 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 877E23858000 for ; Sun, 7 Aug 2022 07:34:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 877E23858000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1659857692; bh=gM2mSGE8B8c09/RRzNPAHEqc0AnHLqjCoWBMXluoXvo=; h=To:Subject:Date:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=ApJFTMk1eeRP3UgAxgHVFQYm6mREUNibdjYU8RJpdXfotI3qyLPXbix63TRNTrFNT dRF0D2lbAO5iAnnjdiFoenztPXkOEdWKV0Sa2fl4U3cAZxso9shyQIC/a/DGBhjjET Lkw5OMkooZabvz3KYw2NAytod5b2i1cMN4+1r4GA= Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by sourceware.org (Postfix) with ESMTPS id 7CE293858294 for ; Sun, 7 Aug 2022 07:34:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7CE293858294 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 2777YMlJ055566; Sun, 7 Aug 2022 02:34:22 -0500 Received: from DFLE102.ent.ti.com (dfle102.ent.ti.com [10.64.6.23]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 2777YMtj062580 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 7 Aug 2022 02:34:22 -0500 Received: from DFLE104.ent.ti.com (10.64.6.25) by DFLE102.ent.ti.com (10.64.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14; Sun, 7 Aug 2022 02:34:22 -0500 Received: from DFLE104.ent.ti.com ([fe80::44c:e883:6f6f:384d]) by DFLE104.ent.ti.com ([fe80::44c:e883:6f6f:384d%17]) with mapi id 15.01.2308.014; Sun, 7 Aug 2022 02:34:22 -0500 To: Andreas Schwab , "Denio, Mike via Gdb" Subject: RE: [EXTERNAL] Re: Confused by watchpoints on remote protocol Thread-Topic: [EXTERNAL] Re: Confused by watchpoints on remote protocol Thread-Index: Adip1GWVQGgzoEbbTR20UHUTp2psZAAUaSQQAAIliXkAAAkoAA== Date: Sun, 7 Aug 2022 07:34:22 +0000 Message-ID: <1c446d6e52484cc8a3ac284726046913@ti.com> References: <87pmhcjz45.fsf@linux-m68k.org> In-Reply-To: <87pmhcjz45.fsf@linux-m68k.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.250.59.181] x-exclaimer-md-config: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Denio, Mike via Gdb" Reply-To: "Denio, Mike" Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" ram_table was just a symbol I created in assembly. Its really odd, and its not the symbol itself. For example: (gdb) watch (uint32_t)ram_table Watchpoint 1: (uint32_t)ram_table (gdb) watch *(uint32_t *)&ram_table Hardware watchpoint 2: *(uint32_t *)&ram_table (gdb) i b Num Type Disp Enb Address What 1 watchpoint keep y (uint32_t)ram_table 2 hw watchpoint keep y *(uint32_t *)&ram_table I can see both of these variants "watching" the exact same address. Maybe you are onto something however. I'll try it with a compiled C program= and see if the behavior is any different. Thanks, Mike -----Original Message----- From: Andreas Schwab =20 Sent: Sunday, August 07, 2022 2:24 AM To: Denio, Mike via Gdb Cc: Denio, Mike Subject: [EXTERNAL] Re: Confused by watchpoints on remote protocol On Aug 07 2022, Denio, Mike via Gdb wrote: > The only question I have is that when I type: > "watch *(uint32_t *)(0x80000018)" > I get a hardware watch point. > > And when I type: > "watch (uint32_t)ram_table" > I get a software watch point. What is ram_table? > Anyone know why? And how to change it to be always hardware? Try looking at breakpoint.c:can_use_hardware_watchpoint. --=20 Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."