Date: Mon, 13 Sep 2004 00:32:26 +1000 From: Sam Lawrance <boris@brooknet.com.au> To: Dan Nelson <dnelson@allantgroup.com> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: sysutils/strace wilderness on 6-CURRENT Message-ID: <1094999545.78235.12.camel@dirk.no.domain> In-Reply-To: <20040831151437.GE33896@dan.emsphone.com> References: <1093948080.29903.14.camel@localhost> <20040831151437.GE33896@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2004-09-01 at 01:14, Dan Nelson wrote: > In the last episode (Aug 31), Vladimir Grebenschikov said: > > (fresh -CURREMT and fresh strace from ports, UP machine) > > > > It silmple does nothing - sleeps foreaver in suspended: > > > > # strace /bin/ls > > ^T > > load: 0.14 cmd: strace 98957 [suspended] 0.00u 0.00s 0% 760k > > ^C > > # > > This has happened on 5.x for ages. The quick fix is to ^Z, then fg, or > kill -CONT the hung strace process from another vty. I don't know what > strace does different from truss that makes it hang. Nowadays, truss > does almost as good a job as strace, so I don't use it as often as I > used to. The only thing I miss is strace's ability to print the name > of blocking syscalls (read or sleep for example) as it waits. When I do "truss -f make install" on a port (I used palm/synce-serial), the process being traced seems to hang (^T shows [stopevent], I haven't looked further than that). If I run without -f, the process doesn't hang. It looks like the process is hanging at a call to vfork(). Maybe it's not just an strace problem? -Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1094999545.78235.12.camel>