Date: Mon, 26 Jun 2017 05:44:52 +0000 From: "Thomas Mueller" <mueller6722@twc.com> To: freebsd-current@freebsd.org Subject: Re: Ports still broken by ino64? Message-ID: <50.A5.03935.85F90595@dnvrco-omsmta01> References: <CAN6yY1uQ6w2CkdM6M2wkOiYQd5-X6HqAsVph7RYCnTKn2mXQeA@mail.gmail.com> <78.25.03057.F5ADD495@dnvrco-omsmta02> <CAN6yY1uv=59cPZDD5H9ZFME54h3npPsYVKU3GjRy37x-ZXn62w@mail.gmail.com> <89.F1.03057.D331E495@dnvrco-omsmta02> <CAJ-VmonzWFXQFw88Ed-1QbA6gS89eNK4%2BMYYaxwyS2TGp%2Bc1EQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50.A5.03935.85F90595>