From: Yao Qi <qiyaoltc@gmail.com>
To: Juha Aaltonen <turbopultti@gmail.com>
Cc: gdb-mailing list <gdb@sourceware.org>
Subject: Re: remote watchpoint
Date: Mon, 09 Nov 2015 15:05:00 -0000 [thread overview]
Message-ID: <868u67xlfo.fsf@gmail.com> (raw)
In-Reply-To: <CAHR0xd6=wmai5rGbnCuN_iQTjUM1FKgCVSpZchz_GO2fS5xt=w@mail.gmail.com> (Juha Aaltonen's message of "Sun, 8 Nov 2015 15:18:00 +0200")
Juha Aaltonen <turbopultti@gmail.com> writes:
> How does a remote server/stub tell gdb which watchpoint fired?
The stub sends stop reply back to GDB with 'watch', 'rwatch' and
'awatch', see details in
https://sourceware.org/gdb/current/onlinedocs/gdb/Stop-Reply-Packets.html
> Also, how does gdb know how many breakpoints/watchpoints are available?
In the remote debugging, GDB doesn't know how many
breakpoint/watchpoints available, but it can tell from the reply of Z
packet. See more descriptions on Z packets
https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html
--
Yao (齐尧)
prev parent reply other threads:[~2015-11-09 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 13:18 Juha Aaltonen
2015-11-09 15:05 ` Yao Qi [this message]
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=868u67xlfo.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=turbopultti@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).