From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/10836] uprobes-provided pt_regs* are unreliable
Date: Tue, 27 Oct 2009 18:40:00 -0000 [thread overview]
Message-ID: <20091027184013.11720.qmail@sourceware.org> (raw)
In-Reply-To: <20091023162529.10836.fche@redhat.com>
------- Additional Comments From roland at gnu dot org 2009-10-27 18:40 -------
"synthesized pt_regs" is a loony concept considered only by systemtap.
It has no place in the general utrace world. user_regset is there, it's what
should be used. The only reason pt_regs is passed into some callbacks is
because the pointer is handy and in some circumstances a few of its fields might
be sufficiently useful for particular code that knows exactly what it is looking
at. General-case code can use the asm/syscall.h macros on it, for example. For
any generalized register access, user_regset is the only right thing to use.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10836
------- 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-10-27 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:25 [Bug uprobes/10836] New: " fche at redhat dot com
2009-10-27 11:44 ` [Bug uprobes/10836] " srikar at linux dot vnet dot ibm dot com
2009-10-27 11:45 ` srikar at linux dot vnet dot ibm dot com
2009-10-27 12:27 ` fche at redhat dot com
2009-10-27 18:40 ` roland at gnu dot org [this message]
2009-10-27 19:17 ` fche at redhat dot com
2009-10-28 12:29 ` mjw at redhat dot com
2009-10-28 16:53 ` jkenisto at us dot ibm dot com
2009-10-28 16:56 ` fche at redhat dot com
2009-10-28 16:59 ` fche at redhat dot com
2009-10-28 18:22 ` roland at gnu dot org
2009-10-29 6:20 ` ananth at in dot ibm dot com
2009-10-29 14:29 ` fche at redhat dot com
2009-11-05 13:57 ` fche at redhat dot com
2009-11-30 20:36 ` 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=20091027184013.11720.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).