I'm sure stas can figure it out!

-a


On 25 June 2017 at 22:44, Thomas Mueller <mueller6...@twc.com> wrote:
> from Adrian Chadd:
>
>> valgrind broke as part of the ino64 work :(
>
> Valgrind was not on my mind!  Your post sent me to
>
> ls -d /usr/ports/*/val*
>
> to find valgrind, and then read the pkg-descr.
>
> One less tool for getting debugging information when something crashes?
>
> Tom
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to