differentiating single-step vs taken-branch trap
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
[email protected]
************************************************************
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com
Weihaw-
1) I don't believe that ptrace' distinguishes between these two events. As far as ptrace' is concerned you've executed a single instruction, taken branch or not. It shouldn't be too hard to infer whether a branch was taken or not. If the current bundle is not 1 greater than the last bundle then a branch was taken, otherwise a branch was most probably not taken. This will miss a branch to the next instruction (seems pretty silly code) or a branch around the one or two instructions that could follow inside the same bundle holding the branch. The two exception cases are pretty rare and you could do some instruction dis-assembly to catch them if you really care.
2) Go to www.linuxia64.com' and follow the link to kernel developers list'. This will lead to the archive for the mailing list. (You posted this message to the IA64 mailing list so obviously the list still exists :-)
Quoted 45 lines · Weihaw Chuang
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
[email protected]************************************************************
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64
Signature · 4 lines
Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale [email protected] Ph: 303/652-0870x117
Hi Wei,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Weihaw Chuang
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
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
Quoted 25 lines · --- David Mosberger
Hi Wei,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
On Sun, 23 Sep 2001 18:43:18 -0700 (PDT),
Weihaw Chuang <[email protected]> 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 toTRAP_BRANCHfor a taken branch and toTRAP_TRACEfor a single step
trap. UsePTRACE_GETSIGINFOto get a hold of the siginfo of the
traced task.
Quoted 1 line
--david
==************************************************************
Weihaw Chuang
[email protected]
************************************************************
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Weihaw Chuang
Wei> In which header file do I find the declaration/definition of Wei> the PTRACE_GETSIGINFO (as well as TRAP_TRACE, TRAP_BRANCH) ? Wei> I'm using a machine with 2.4.0 kernel. Would this rather old Wei> kernel be the reason why?
It comes from <sys/ptrace.h>. If it's not there, you need to upgrade your glibc. A newer kernel wouldn't hurt either, though...
--david