Date: Tue, 5 Mar 2019 16:43:43 +0100 From: Serpent7776 <serpent7776@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: devel/valgrind not working Message-ID: <20190305164343.109d3986@DaemONX> In-Reply-To: <ea61170d-f5d5-ad7b-c488-7f067b387cbd@netfence.it> References: <ea61170d-f5d5-ad7b-c488-7f067b387cbd@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Mar 2019 17:27:45 +0100 Andrea Venturoli <ml@netfence.it> wrote: > Hello. > > I've been using valgrind for a long time. > After some months without using it, today it does not work anymore. > > > # freebsd-version -ku > > 11.2-RELEASE-p9 > > 11.2-RELEASE-p8 > > # uname -p > > amd64 > > # pkg info | grep valgrind > > valgrind-3.10.1.20160113_7,1 Memory debugging and profiling tool > > # valgrind --version > > valgrind-3.10.1 > > # valgrind ls > > ==15396== Memcheck, a memory error detector > > ==15396== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > > ==15396== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info > > ==15396== Command: ls > > ==15396== > > Bad system call (core dumped) > > Reading the core doesn't give any useful info. > Same goes for devel/valgrind-devel. > > Any hint? Working fine for me with same setup with exception of patch level which is both -p9. Maybe your userland is out of sync with the kernel? # freebsd-version -ku 11.2-RELEASE-p9 11.2-RELEASE-p9 > > bye & Thanks > av. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- /* * Serpent7776 */
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190305164343.109d3986>