Re: [sct-hackers] Syscalltrack and debugging issues

[Orna A. <lad...@gr...>]

On Fri, 18 Jun 2004, Marcio O. Buss wrote:

> Date: Fri, 18 Jun 2004 12:03:21 -0400 (EDT)
> From: Marcio O. Buss <ma...@cs...>
> To: sys...@li...
> Subject: [sct-hackers] Syscalltrack and debugging issues
>
>
> Hi all,
>
> I am new to the area, and am looking for a software package
> the solve a debugging issue that I am not sure is feasible.
> In short, I would like to be able to intercept a system call
> and determine which command/funcion call in what C source
> file within the running application exercised that system
> call. More precisely, for debugging purposes I would like
> to be able to point out which line of source code was
> responsible for a given type of system call. I imagine
> compiling the source code using a "-g" like option and
> then figuring this all out.
>
> Any help would be appreciated,
> Thanks,
> -Marcio.
>

How about hijacking the system call using syscalltrack, and then
attaching gdb to it?

Though I think this should require interfering with the code excuted
before (or after) the system call - I don't think there is a ready
mechanism for that, is there?

Orna.