Re: [rfc] catch syscall

[Daniel Jacobowitz <drow@false.org>]

On Fri, Jul 06, 2007 at 07:48:06PM -0400, Alan Curry wrote:
> >> We just need to keep track of a single bit of extra state for each inferior
> >> thread, to know what type of syscall event is expected next. I'm just having
> >> a hard time finding where per-inferior-thread information is supposed to be
> >> stored.
> >
> >This would probably be Linux-specific data, at least for now.  Take a
> >look at the LWP list in linux-nat.c.
> 
> If we want the generic code in inf-ptrace.c to behave differently (for
> example using PTRACE_SYSCALL instead of PTRACE_SINGLESTEP) depending on the
> value of a flag in that Linux-specific data, how do we get at it? Add another
> target method to return the flag? I noticed when doing this patch that adding
> a target method involves changing code in several different places.

I don't know.  The best answer may be to not use the generic routine
any more.  There is not much of one, and some of it (the ptid check)
is not required with the linux-nat usage.

-- 
Daniel Jacobowitz
CodeSourcery