Bug 1605

Summary: single step a system call
Product: frysk Reporter: Andrew Cagney <cagney>
Component: generalAssignee: Unassigned <frysk-bugzilla>
Status: NEW ---    
Severity: normal CC: sm
Priority: P1    
Version: unspecified   
Target Milestone: ---   
Host: Target:
Build: Last reconfirmed:
Bug Depends on: 1524    
Bug Blocks: 1521    

Description Andrew Cagney 2005-10-29 02:58:12 UTC
This needs to check both with, and without, system call tracing enabled.
Comment 1 Mark Wielaard 2007-02-13 13:25:33 UTC
System call tracing is difficult with ptrace singlestep since you won't get
separate events anymore for syscall enter/exit. This could however be simulated
by generializing the Isa.isAtSyscallSigReturn() method to return the syscall the
current pc is on during stepping.

This however depends on syscall enter/exit events (and it particular the syscall
number/name, result and arguments passing) being properly done through the TaskO
bserver.Syscall interface and the associated Task.getSyscallEventInfo() method.
Comment 2 lissacoffey 2016-06-11 07:10:20 UTC Comment hidden (spam)