Re: [patch]: inform user that a watchpoint is hit

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Thu, 27 Aug 2009 09:36:55 +0200, Chandru wrote:
> Chandru wrote:
>> whereas gdb-6.8.50.20090824 doesn't.
>>
>> Program exited normally.
>> (gdb) r
>> Starting program: /home/chandru/rawatch
>>
>> Breakpoint 1, main () at rawatch.c:20
>> 20          value1 =3;
>> (gdb)

You did not paste a complete log of GDB from its start. I do not know what is
rawatch.c, I do not know where exactly did you put "Breakpoint 1" etc.

If line 20 is the first line of code of main and you did "break main" then it
is correct the first breakpoint/watchpoint hit is that in main as there could
not be hit any watchpoints before the first line of code being executed.


>> It is not the case that the read or access watchpoints are not being hit.
>> Just the messages like 'Hardware read watchpoint 2: value1' and
>> 'Hardware access (read/write) watchpoint 3: value1'  are not shown
>> on the screen when the program is restarted

As the line 20 is hit before any of the watchpoints are hit it is correct GDB
shows only "Breakpoint 1" at that moment.  If you do "continue" GDB should
show some of the watchpoints get hit.


>> It is only the first occurrence of the
>> watchpoints that the messages don't get displayed for.

I do not see any copy-paste showing any wrong behavior for gdb-6.8.50.20090824.
My tests also did not reproduce any wrong behavior.


> does this make sense or we need to do nothing over here ?,

Only gdb-6.8.50.20090824 is relevant here.  We cannot change gdb-6.6 even if
it was buggy.


Regards,
Jan