From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] differentiating single-step vs taken-branch trap
Date: Mon, 24 Sep 2001 16:42:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805243@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805241@msgid-missing>
Hi Wei,
>>>>> On Sun, 23 Sep 2001 18:43:18 -0700 (PDT), Weihaw Chuang <weihaw@yahoo.com> said:
Wei> Hi everyone, I've got two questions, but only the first is
Wei> really important. 1. I'm using the ptrace kernel interface to
Wei> trace a child process via single-step or taken-branch traps
Wei> (through David Mosberger's utrace tool). Is there a way I can
Wei> use ptrace to allow me to single-step, and in addition observe
Wei> occurances of taken-branches?
Yes, the siginfo trap code (si_code) will tell you. It is set to
TRAP_BRANCH for a taken branch and to TRAP_TRACE for a single step
trap. Use PTRACE_GETSIGINFO to get a hold of the siginfo of the
traced task.
--david
next prev parent reply other threads:[~2001-09-24 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 1:43 [Linux-ia64] differentiating single-step vs taken-branch trap Weihaw Chuang
2001-09-24 14:46 ` n0ano
2001-09-24 16:42 ` David Mosberger [this message]
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-105590698805243@msgid-missing \
--to=davidm@hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.