Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chandru <chandru@in.ibm.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch]: inform user that a watchpoint is hit
Date: Sat, 15 Aug 2009 12:22:00 -0000	[thread overview]
Message-ID: <4A869488.2060407@in.ibm.com> (raw)
In-Reply-To: <e394668d0908141722l2ae205f8m97e1218ebd2b39c4@mail.gmail.com>

Doug Evans wrote:
> On Fri, Aug 14, 2009 at 3:32 AM, Chandru<chandru@in.ibm.com> wrote:
>   
>> When a program is restarted within gdb, the initial breakpoint hit messages are
>> not outputted on to the screen. Inform the user that a watchpoint has been hit
>>
>> Signed-off-by: Chandru Siddalingappa <chandru@ilinux.vnet.ibm.com>
>> ---
>>
>> --- gdb/breakpoint.c.orig       2009-08-14 17:53:06.000000000 +0530
>> +++ gdb/breakpoint.c    2009-08-14 17:54:02.000000000 +0530
>> @@ -842,6 +842,9 @@ update_watchpoint (struct breakpoint *b,
>>   struct bp_location *loc;
>>   bpstat bs;
>>
>> +  if (breakpoint_enabled (b))
>> +      mention(b);
>> +
>>   unlink_locations_from_global_list (b);
>>   for (loc = b->loc; loc;)
>>     {
>>
>>     
>
> Hi.
> If we're stopping because of a watchpoint and not reporting it, that's bad.
> But it seems odd that this is happening, and simple experiments don't
> reveal anything.
> Do you have a testcase?
>   
yes,

The steps performed to reproduce are:

1) Compile the following program with debug info
2) Run the program.
3) Set a watchpoint for "value1" variable.
4) Run the test and do some checks. 
5) Program exits. Now restart the program execution
6) Expect to see the message of hitting the watchpoint for value1 in main () line 20.

#include <stdio.h>
#include <stdlib.h>

 int value1 = -1;
 int value2 = -1;

 int func1 ()
 {
    value1=2;
    value2=value1;
      return 0;

 }


 int main ()
 {
    int i;

    value1 =3;
    value2 = value1;
    for (i=0; i<2; i++) {
      value1 = i;
      value2 = value1;
    }

    func1();

     return 0;
 }


---------------

(gdb) break main
Breakpoint 1 at 0x8048453: file rawatch.c, line 20.
(gdb) run
Starting program: /home/vrvazque/rawatch

Breakpoint 1, main () at rawatch.c:20
20          value1 =3;
(gdb) rwatch value1
Hardware read watchpoint 2: value1
(gdb) awatch value1
Hardware access (read/write) watchpoint 3: value1
(gdb) cont
Continuing.
Hardware access (read/write) watchpoint 3: value1

Old value = -1
New value = 3
0x08048462 in main () at rawatch.c:21
21          value2 = value1;
(gdb) cont
...
...
...
(gdb) cont
Continuing.

Program exited normally.
(gdb) run
Starting program: /home/vrvazque/rawatch

Breakpoint 1, main () at rawatch.c:20
20          value1 =3;
(gdb) cont


  reply	other threads:[~2009-08-15 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 13:15 Chandru
2009-08-15 10:57 ` Doug Evans
2009-08-15 12:22   ` Chandru [this message]
2009-08-18 17:31     ` Doug Evans
2009-08-19  8:05       ` Chandru
2009-08-19 13:03         ` Jan Kratochvil
2009-08-24 11:27           ` Chandru
2009-08-27  7:45             ` Chandru
2009-08-27  8:26               ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A869488.2060407@in.ibm.com \
    --to=chandru@in.ibm.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox