devel/valgrind not working
Serpent7776
serpent7776 at gmail.com
Tue Mar 5 15:44:34 UTC 2019
On Mon, 4 Mar 2019 17:27:45 +0100
Andrea Venturoli <ml at 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
--
/*
* Serpent7776
*/
More information about the freebsd-ports
mailing list