Am Dienstag, 11. April 2006 17:52 schrieb Dan Nelson:
> In the last episode (Apr 11), Jonas Wolz said:
> > If I call "truss -f sh test.sh" I get errors when execve() is called
> > to start /bin/echo, for example: (56179 is the first /bin/echo
> > (started without error), 56178 is /bin/sh)
>
> I thi
In the last episode (Apr 11), Jonas Wolz said:
> Am Montag, 10. April 2006 11:45 schrieb Jonas Wolz:
> > Other applications I tested (xedit, bash) seem to work fine.
>
> I've made some more tests and it seems to me that the "fork
> following" feature (-f switch) of truss obviously is buggy. Even t
Am Montag, 10. April 2006 11:45 schrieb Jonas Wolz:
> Other applications I tested (xedit, bash) seem to work fine.
I've made some more tests and it seems to me that the "fork following" feature
(-f switch) of truss obviously is buggy.
Even the following simple shell script sometimes (in about a t
Jonas Wolz <[EMAIL PROTECTED]> wrote:
> while trying to get the gnash CVS version to work I noticed that on
> my system (FreeBSD 6.0-RELEASE) truss obviously has problems tracing
> firefox: truss prints somewhat "random" error messages and traces
> only some of the system calls firefox makes (open
Hello,
while trying to get the gnash CVS version to work I noticed that on my system
(FreeBSD 6.0-RELEASE) truss obviously has problems tracing firefox:
truss prints somewhat "random" error messages and traces only some of the
system calls firefox makes (opening a local file doesn't show up, for
