From: Simon Sobisch <simonsobisch@gnu.org>
To: gdb@sourceware.org
Subject: How/where is the mi watchpoint-trigger / EXEC_ASYNC_WATCHPOINT_TRIGGER raised?
Date: Mon, 19 Jul 2021 17:49:32 +0200 [thread overview]
Message-ID: <532367b4-bd4c-8468-03a5-418591bbefb3@gnu.org> (raw)
In-Reply-To: <f1e33049-aa36-07d3-709d-642f74d49ffd@gnu.org>
I've found the definition in mi/mi-common.h and the translation in
mi/mi-common.c, but I have no clue:
1 Understanding GDB:
Where is it actually raised? (I _assume_ it somewhere happens if a
watchpoint's stop method returns True?
2 Extending GDB:
Can I manually trigger the event from a breakpoint? The reasoning behind
this is that my watchpoint implementation always returns False after
setting a breakpoint at the place where the user "expects" to see the
change (when returning to user code, not multiple times in the library
code). While it "looks" nice on the GDB console MI-Frontends don't get
any watchpoint events that way.
Thanks
Simon
next prev parent reply other threads:[~2021-07-19 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 22:24 Is it possible to "inject" into the stack or show non-stack entries via frame decorator api? Simon Sobisch
2021-07-17 14:22 ` Simon Sobisch
2021-07-19 15:49 ` Simon Sobisch [this message]
2021-11-28 15:40 ` Simon Sobisch
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=532367b4-bd4c-8468-03a5-418591bbefb3@gnu.org \
--to=simonsobisch@gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).