Bug 1605 - single step a system call
Summary: single step a system call
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Unassigned
Depends on: 1524
Blocks: 1521
  Show dependency treegraph
Reported: 2005-10-29 02:58 UTC by Andrew Cagney
Modified: 2016-06-11 07:10 UTC (History)
1 user (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
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)