Date: Mon, 26 Jun 2017 14:18:42 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Thomas Mueller <mueller6722@twc.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Ports still broken by ino64? Message-ID: <CAJ-Vmom89Rbv%2BMCOKkwdGHVq0Ei6TDs8AXAXym427PtM-Xb5Lw@mail.gmail.com> In-Reply-To: <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> <50.A5.03935.85F90595@dnvrco-omsmta01>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm sure stas can figure it out! -a On 25 June 2017 at 22:44, Thomas Mueller <mueller6722@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-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom89Rbv%2BMCOKkwdGHVq0Ei6TDs8AXAXym427PtM-Xb5Lw>