From: Weihaw Chuang <weihaw@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] differentiating single-step vs taken-branch trap
Date: Mon, 24 Sep 2001 01:43:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805241@msgid-missing> (raw)
Hi everyone,
I've got two questions, but only the first is really
important.
1. I'm using the ptrace kernel interface to trace a
child process via single-step or taken-branch traps
(through David Mosberger's utrace tool). Is there a
way I can use ptrace to allow me to single-step, and
in addition observe occurances of taken-branches?
It seems that its possible to set the PSR.SS and
PSR.TB concurrently, but not a way of differentiating
the returned trap signal. All we know upon returning
from wait is that a trap occured.
Although it seems redundant, as far as I know there is
a subtle difference between taken-branch traps and
single-step traps. Taken-branch traps return back an
IIP value of the branch target, before committing the
the results of the target instruction. Single-step
traps assign IIP of the committed instruction. The
difference is important if I want to look ahead to get
register state before a memory operation commits any
registers writes.
2. Is there still a ia64 linux kernel mailing list?
And is it archived somewhere?
Many thanks,
-Wei
==************************************************************
Weihaw Chuang
wchuang@cs.ucsd.edu
************************************************************
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com
next reply other threads:[~2001-09-24 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 1:43 Weihaw Chuang [this message]
2001-09-24 14:46 ` [Linux-ia64] differentiating single-step vs taken-branch trap n0ano
2001-09-24 16:42 ` David Mosberger
2001-09-24 17:53 ` Weihaw Chuang
2001-09-24 18:03 ` David Mosberger
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=marc-linux-ia64-105590698805241@msgid-missing \
--to=weihaw@yahoo.com \
--cc=linux-ia64@vger.kernel.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