Re: ecl and SIGNALS

2013-03-10 Thread Christoph Egger
Christoph Egger writes: > As suggested by Michael Banck on IRC I've been looking at Signals used > by both parts to see if they e.g. battle over SIGUSR?. However libgc > seems to use 32+{5,6} as signals on x86 FREEBSD __GLIBC__ at > least. Petr, Steven: any idea why this is? Are these signals fi

ecl and SIGNALS

2013-03-10 Thread Christoph Egger
Hi! As suggested by Michael Banck on IRC I've been looking at Signals used by both parts to see if they e.g. battle over SIGUSR?. However libgc seems to use 32+{5,6} as signals on x86 FREEBSD __GLIBC__ at least. Petr, Steven: any idea why this is? Are these signals fine for kfreebsd glibc (signa

Re: Porting valgrind to Debian/kFreeBSD

2013-03-10 Thread Jeff Epler
I cleaned up the freebsd diffs, added some magic from this thread, and filed a debbug about it (702729). I'm not 100% confident it won't cause some debian/linux regression or that it's complete, but it's a step in the right direction, particularly as it builds off of the version of valgrind presen

Re: Porting valgrind to Debian/kFreeBSD

2013-03-10 Thread Jeff Epler
It looks like freebsd9 ports has "valgrind-snapshot" which is based off of valgrind 3.8.0: http://cdn.bitbucket.org/stass/valgrind-freebsd/downloads/valgrind-freebsd-3.8.0.tar.bz2 There are a lot more changes than I would expect between this and the upstream 3.8.0 tarball: valgrind-3.8.0/FAQ.txt

Re: Porting valgrind to Debian/kFreeBSD

2013-03-10 Thread Alessandro Ghedini
On Thu, Mar 07, 2013 at 09:00:42PM +0100, Carlos Alberto Lopez Perez wrote: > I'm not sure if this means that we can finally have valgrind packaged > for Debian/kFreeBSD. > > > The diffstat between "official" valgrind and this freebsd port is pretty > big. Is there any chance that the author(s)