From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Shrikanth Kamath <shrikanth07@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB hardware watchpoint information on i386
Date: Mon, 02 Aug 2010 08:09:00 -0000 [thread overview]
Message-ID: <20100802080932.GA15770@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTim7=AoN7Mi5L=Q8tTbvn1_3xzhK7V8OfDvj1BUQ@mail.gmail.com>
On Mon, 02 Aug 2010 09:55:02 +0200, Shrikanth Kamath wrote:
> I mean there would be
> foo_service_watchpoint()
> {
> /* map actions to this watchpoint */
> }
>
> which is this function?
It is caught by bpstat_stop_status but you should not touch the existing
breakpoint list there. Otherwise print_it_typical but I am not completely
sure you cannot miss the watchpoint in some cases of multiple events at once
(but the same applies for normal watchpoints themselves).
Anyway I do not much understand why don't you connect externally.
Jan
next prev parent reply other threads:[~2010-08-02 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 4:10 Shrikanth Kamath
2010-08-02 5:53 ` paawan oza
2010-08-02 6:58 ` Jan Kratochvil
2010-08-02 7:55 ` Shrikanth Kamath
2010-08-02 8:09 ` Jan Kratochvil [this message]
2010-08-02 8:16 ` paawan oza
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=20100802080932.GA15770@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=shrikanth07@gmail.com \
/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