Date: Wed, 17 Oct 2007 17:37:09 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-current <freebsd-current@FreeBSD.org>, Michael Butler <imb@protected-networks.net>, Simon Barner <barner@FreeBSD.org> Subject: Re: another gcc 4.2 breakage? Message-ID: <48796.1192642629@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 17 Oct 2007 19:31:58 %2B0200." <4716470E.9010101@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4716470E.9010101@FreeBSD.org>, Kris Kennaway writes: >> I have a compile fix for this problem -- the resulting binary dumps >> core though. I can commit the fix and mark the port IGNORE on RELENG_7 >> until we have a proper solution. I don't think a proper solution will happen, until we get a new port based on more recent valgrind code. We could use more hands getting all our syscalls implemented in valgrind, so volunteers are more than welcome help out in //depot/projects/valgrind/... Last I had a couple of days to spend, I got as far as running thr/umtx based multi-threaded programs. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48796.1192642629>