From mboxrd@z Thu Jan  1 00:00:00 1970
From: Weihaw Chuang <weihaw@yahoo.com>
Date: Mon, 24 Sep 2001 17:53:29 +0000
Subject: Re: [Linux-ia64] differentiating single-step vs taken-branch trap
Message-Id: <marc-linux-ia64-105590698805244@msgid-missing>
List-Id: <linux-ia64.vger.kernel.org>
References: <marc-linux-ia64-105590698805241@msgid-missing>
In-Reply-To: <marc-linux-ia64-105590698805241@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-ia64@vger.kernel.org

In which header file do I find the
declaration/definition of the PTRACE_GETSIGINFO (as
well as TRAP_TRACE, TRAP_BRANCH) ?  I'm using a
machine with 2.4.0 kernel.  Would this rather old
kernel be the reason why?

-Wei


--- David Mosberger <davidm@hpl.hp.com> wrote:
> 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


==************************************************************

Weihaw Chuang
wchuang@cs.ucsd.edu

************************************************************

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com