From: Phil Muldoon <pmuldoon@redhat.com>
To: Frysk Hackers <frysk@sourceware.org>
Subject: TaskState handleTrappedEvent
Date: Wed, 24 Oct 2007 15:10:00 -0000 [thread overview]
Message-ID: <471F603F.2090703@redhat.com> (raw)
I noticed that this state is getting a little more crowded and will be
even more crowded soon with watchpoints. Before I add my own patches
here, some questions:
1) Is there an important order precedence here? Must it handle single
step over breakpoints over watchpoints in any particular order? I can't
think of why the order matters.
2) I'm a little fuzzy on if there were will be an opportunity for
multiple events to happen on a single sigtrap (ie breakpoint and
watchpoint). I cannot think of any right now other than single step
writing something to a memory address that the watchpoint is monitoring,
but that should be caught on as another later sigtrap. Are there
opportunities for multiple events? If so, are there any precedence issues?
Regards
Phil
next reply other threads:[~2007-10-24 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 15:10 Phil Muldoon [this message]
2007-10-29 10:58 ` Mark Wielaard
2007-10-30 15:48 ` Phil Muldoon
2007-11-05 22:20 ` Mark Wielaard
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=471F603F.2090703@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@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).