This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: breakpoints/2332: watchpoints silently don't work on Opteron
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 11 Oct 2007 19:28:01 -0000
- Subject: Re: breakpoints/2332: watchpoints silently don't work on Opteron
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR breakpoints/2332; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: yuri@tsoft.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: breakpoints/2332: watchpoints silently don't work on Opteron
Date: Thu, 11 Oct 2007 15:22:58 -0400
On Thu, Oct 11, 2007 at 07:14:19PM -0000, yuri@tsoft.com wrote:
> I am trying to set watchpoint on my Opteron (see log below).
> Though this value has been changed watchpoint didn't occur.
>
> gdb should either catch watchpoint or tell the user that watchpoints don't work and why they don't work when user sets a watchpoint.
>
> Otherwise it looks completely broken.
They work fine for me on a comparable system with a newer kernel.
> (gdb) p &i
> $1 = (int *) 0x7fbfffeb0c
> (gdb) watch 0x7fbfffeb0c
> Watchpoint 2: 548682066700
That is not doing what you think. Try watch *(int *)0x7fbfffeb0c.
The value "0x7fbfffeb0c" is not changing.
--
Daniel Jacobowitz
CodeSourcery