On Mon, Jul 27, 2020 at 09:49:57PM -0500, Kyle Evans wrote:
> On Fri, Jul 24, 2020 at 3:24 PM Kyle Evans wrote:
> >
> > Hello!
> >
> > Just a little bit ago, I committed an update[0] to the valgrind-devel
> > port that updates it to Paul Floyd's branch,
On Fri, Jul 24, 2020 at 3:24 PM Kyle Evans wrote:
>
> Hello!
>
> Just a little bit ago, I committed an update[0] to the valgrind-devel
> port that updates it to Paul Floyd's branch, where he has rebased us
> forward to 3.17.0 and largely fixed valgrind operation on b
Hello!
Just a little bit ago, I committed an update[0] to the valgrind-devel
port that updates it to Paul Floyd's branch, where he has rebased us
forward to 3.17.0 and largely fixed valgrind operation on both 12.x
and -CURRENT.
He's put in significant effort to get the test suite
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
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
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
> FreeBS
uld 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 ke
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-lic
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 lookin
