RE: [EXTERNAL] Re: Confused by watchpoints on remote protocol

Denio, Mike via Gdb
2022-08-07T14:44:13Z

I verified with a compiled C program, the watch always uses a hardware watch.

Not sure what it doesn't like about my assembly, but it obviously has nothing to do with my GDB server, so pressing on ...

Thanks for the suggestion.

Mike

-----Original Message-----
From: Denio, Mike <>
Sent: Sunday, August 07, 2022 2:34 AM
To: 'Andreas Schwab' <schwab@linux-m68k.org>; Denio, Mike via Gdb <gdb@sourceware.org>
Subject: RE: [EXTERNAL] Re: Confused by watchpoints on remote protocol

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 <schwab@linux-m68k.org>
Sent: Sunday, August 07, 2022 2:24 AM
To: Denio, Mike via Gdb <gdb@sourceware.org>
Cc: Denio, Mike <miked@ti.com>
Subject: [EXTERNAL] Re: Confused by watchpoints on remote protocol