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: Wed, 19 Aug 2009 08:05:00 -0000 [thread overview]
Message-ID: <4A8BB035.6030601@in.ibm.com> (raw)
In-Reply-To: <e394668d0908181009x73d887a9j530b3cc6e257f9f6@mail.gmail.com>
Doug Evans wrote:
> So in cvs head I'm not seeing a problem (though maybe there's more
> needed to recreate it).
> Which version of gdb are you using?
>
> [Also, I haven't researched this, but maybe there's some overlap here with
> http://sourceware.org/ml/gdb-patches/2009-08/msg00254.html.
> Dunno. Doesn't seem like it but thought I'd point it out.]
>
Hello Doug,
Thanks for trying the test program. What I was referring to was
the messages like the following to be outputted on the screen with
the patch applied..
Program exited normally.
(gdb) r
Starting program: /home/chandru/r
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Hardware access (read/write) watchpoint 2: value1
Hardware read watchpoint 3: value1
Breakpoint 1, main () at rwatch.c:20
20 value1 =3;
(gdb)
I was using a distribution supplied gdb-6.8.50 and found that upstream
gdb shows the same behaviour. gdb-6.6 outputs these messages
without the patch when a program is restarted.
Thanks,
Chandru
next prev parent reply other threads:[~2009-08-19 7:56 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
2009-08-18 17:31 ` Doug Evans
2009-08-19 8:05 ` Chandru [this message]
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=4A8BB035.6030601@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