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 x86&linux 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 Sundberg    Address: 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

Reply via email to