Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Aug 2004 12:23:55 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Gary Jennejohn <garyj@www.jennejohn.org>
Cc:        "current@freebsd.org" <current@FreeBSD.org>
Subject:   Re: sysutils/strace wilderness on 6-CURRENT
Message-ID:  <20040831172354.GF33896@dan.emsphone.com>
In-Reply-To: <200408311705.i7VH5R2A073646@peedub.jennejohn.org>
References:  <20040831151437.GE33896@dan.emsphone.com> <200408311705.i7VH5R2A073646@peedub.jennejohn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 31), Gary Jennejohn said:
> Dan Nelson writes:
> > In the last episode (Aug 31), Vladimir Grebenschikov said:
> > > It silmple does nothing - sleeps foreaver in suspended:
> > > 
> > > # strace /bin/ls
> > 
> > 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.
> > 
> 
> I fixed a bug like this in strace for Linux. The SIGCHLD handler was
> being set too late and the child (through some wacky handling of
> SIGCHLD in the Linux kernel) got into a state where it never returned
> the expected status in wait(). Both the child and strace ended up
> hanging. kill -CONT also got things going there. Maybe FreeBSD has a
> similar problem?

Dunno.  Strace is a port built from the sources at sourceforge, so I
assume that any Linux fixes would also be included.  I see the port is
at 4.5.1 but sourceforge is up to 4.5.7.  Maybe a newer version works
better?

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040831172354.GF33896>