From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16164 invoked by alias); 13 Feb 2007 13:25:48 -0000 Received: (qmail 15756 invoked by uid 48); 13 Feb 2007 13:25:33 -0000 Date: Tue, 13 Feb 2007 13:25:00 -0000 Message-ID: <20070213132533.15755.qmail@sourceware.org> From: "mark at klomp dot org" To: frysk-bugzilla@sourceware.org In-Reply-To: <20051029025812.1605.cagney@redhat.com> References: <20051029025812.1605.cagney@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/1605] single step a system call X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00361.txt.bz2 List-Id: ------- Additional Comments From mark at klomp dot org 2007-02-13 13:25 ------- 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. -- What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |1524 http://sourceware.org/bugzilla/show_bug.cgi?id=1605 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.