From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/5273] x86 arch_validate_probed_insn(): lighten up?
Date: Fri, 24 Apr 2009 21:00:00 -0000 [thread overview]
Message-ID: <20090424210014.28695.qmail@sourceware.org> (raw)
In-Reply-To: <20071105215923.5273.jkenisto@us.ibm.com>
------- Additional Comments From jkenisto at us dot ibm dot com 2009-04-24 21:00 -------
uprobes/uprobes_i386.c has been brought back into sync with the (more tolerant)
uprobes2/uprobes_x86.c. A couple of changes were ad hoc to address specific
test failures. Commit af6b060 completes the resync.
We still haven't done any exhaustive testing of the whole instruction set.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5273
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-04-24 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:59 [Bug uprobes/5273] New: " jkenisto at us dot ibm dot com
2009-04-24 21:00 ` jkenisto at us dot ibm dot com [this message]
2009-08-13 17:47 ` [Bug uprobes/5273] " fche at redhat dot com
[not found] <bug-5273-6586@http.sourceware.org/bugzilla/>
2015-01-29 1:33 ` fche at redhat dot com
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=20090424210014.28695.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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).