strace broken in 7.0?
tabthorpe at freebsd.org
Thu Jan 10 12:58:04 PST 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 10 January 2008 14:15:48 Timo Schoeler wrote:
> Thus Julian Elischer <julian at elischer.org> spake on Thu, 10 Jan 2008
> 10:59:54 -0800:
> > Tom Evans wrote:
> > > On Thu, 2008-01-10 at 18:11 +0100, Philippe Audéoud wrote:
> > >> On Thu, 10 Jan 2008, Unga wrote:
> > >>> Hi all
> > >>>
> > >>> strace (v4.5.5) works well in 6.2. But strace (v4.5.6)
> > >>> develops following error in 7.0-PRERELEASE:
> > >>> $ strace pwd
> > >>> execve(0xbfbfe92c, [0xbfbfedf4], [/* 0 vars
> > >>> */]PIOCWSTOP: Input/output error
> > and the reason you don't use ktrace is..?
> I tried to hide, really. But this is a perfect example of what the
> bsdforen.de discussion is about.
Before we start signalling the apocolypse of FreeBSD because an out of date
port was not updated on somebodies system, let us gather our wits about us.
I am the maintainer of strace and I came in late on this thread. The port was
updated last on December 30, and AFAIK 4.5.7 works on supported platforms.
I may be some naive Canadian kid, however, the last time I checked, accepted
practises what they are, if you have an issue/problem/concern with a port,
you follow up with the port maintainer first. Unfortunately, I only found out
about this issue via a pop-up in IRC, informing me there was something
brewing in -current, and I should check it out.
I have read John Baldwin's email about patches he has, and now that I know, I
Anyway, I will step out of the pulpit now.
Thomas Abthorpe | FreeBSD Ports Committer
tabthorpe at FreeBSD.org | http://people.freebsd.org/~tabthorpe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the freebsd-current