Re: valgrind
I'm working on porting this right now. 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. Afaik, the patches can remain part of the ports tree without problems. -- Matthew Emmerton || [EMAIL PROTECTED] GSI Computer Services || http://www.gsicomp.on.ca On Wed, 27 Feb 2002, Patrik Sundberg wrote: hi, I found this tool called valgrind (http://devel-home.kde.org/~sewardj/) a few days ago and find it really interesting. It is something similair to purify (memory use debugger one could call it I guess) but GPL'ed and developed by the KDE team from what I can tell. I have been looking for this kind of tool for a long time and haven't found one I really like yet. As it is right now valgrind is x86linux 2.4 specific (probably gcc specific too..) but I would really love to see a FreeBSD port. It should be quite possible to port the OS specific parts to handle FreeBSD systemcalls instead of Linux ones. Is anyone already looking in to this or interested? It would be a great tool to debug the base system with as well as your own applications. -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: valgrind
On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote: I'm working on porting this right now. great news! what is the current status and have you set up a website for the project or will it be a simple portsentry with some patches? (I thought it would require some more rewriting than a usual port+patches, but I could be wrong, haven't looked at the code yet). 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. as long as it can exist in the ports-collection I will be more than pleased. -- ---. Patrik SundbergAddress: Rydsvägen 100C, 584 31 Linköping, Sweden | Email: [EMAIL PROTECTED] || [EMAIL PROTECTED] | Phone: +46 13 178567 || +46 707 602240| .--- Applied Physics and Electrical Engineering student | |- Master of Science in Business Administration and Economics student | |--- UNIX/Programming consultant | `--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: valgrind
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 [EMAIL PROTECTED], [EMAIL PROTECTED] my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: valgrind
Matthew Emmerton wrote: I'm working on porting this right now. 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. Afaik, the patches can remain part of the ports tree without problems. Add a dlopen-based module interface? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: valgrind
Michael Lucas wrote: 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. No, it can't. You can't change the license on the original code, or you lose your rights granted under that license. The only thing that works for swallowing is an aggregate license. In the vgrind case, that is not an option. 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. :-) Distribution of the binary is a problem as long as there is a license miscibility issue. Distribution of the components is allowed. As an example, you can't build a FreeBSD with a statically linked IBM JFS port in it (and therefore you can't boot from an IBM JFS with a distribution kernel), but you can distribute an IBM JFS as a binary kernel module with accompanying source code (all under the GPL). Doing this really skirts dangerously close to the interface GPL'ing issue that FSF used to try and beat some crypto into GPL-land; I would not want to be a test case for this. This is why FreeBSD lets people use GPL'ed components as an after market item, but does not distribute them: it is in the ditribution that the clause activates. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
