Date: Wed, 27 Feb 2002 11:42:39 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Matthew Emmerton <matt@gsicomp.on.ca> Cc: Patrik Sundberg <ps@radiac.mine.nu>, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: valgrind Message-ID: <20020227114239.A63680@blackhelicopters.org> In-Reply-To: <Pine.BSF.4.21.0202271056400.45612-100000@xena.gsicomp.on.ca>; from matt@gsicomp.on.ca on Wed, Feb 27, 2002 at 11:00:14AM -0500 References: <20020227151310.GA47084@raquel.radiac.mine.nu> <Pine.BSF.4.21.0202271056400.45612-100000@xena.gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote: > Be forewarned, though, that the FreeBSD hacks for this tool will > *never* be allowed into the main distro. Why? Licence. Valgrind > includes some code from the Linux kernel and libc. When we hack it for > FreeBSD, we'll end up putting some BSD-licenced code into a GPL > product. Obviously, this will cause problems. Actually, this doesn't cause as many as you might think. GPL'd code can swallow BSDL'd code. BSDL'd code cannot swallow GPL'd code. You could probably get your code assimilated into the main valgrind distro. FreeBSD also includes (among others) gdb, which is GPL'd. Since valgrind is not necessary to run a minimal FreeBSD install, it's OK. (Note that I'm not advocating assimilating it into the main system, I'm just saying that the license isn't an impediment. :-) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020227114239.A63680>