Re: devel/valgrind not working [SOLVED]
On 3/5/19 5:26 PM, Andrea Venturoli wrote: I'll try rebuilding and reinstalling world (even if it should not really change, apart from version number); if something different happens I'll report back. As expected, upgrading world from 11.2p8 to 11.2p9 did not change anything. I had a suggestion off-list which solved: valgrind needs COMPAT_FREEBSD10 in the kernel configuration. I thought I didn't need this and had removed it. Altough this options comes in GENERIC, I'd suggest mentioning it in pkg message. 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-unsubscr...@freebsd.org"
Re: devel/valgrind not working
On 3/5/19 5:06 PM, Kurt Jaeger wrote:
Which begs the question: for which kernel was valgrind compiled ?
I had the original problem in a jail on machine "A"; valgrind was
compiled on an identical machine ("B") with Poudriere.
Machine "A" and "B" run the same kernel and userland (the latter
compiled for both on machine "B").
As a test, I also installed valgrind with portupgrade on machine "B"
(the one that runs Poudriere): the text I pasted comes from this setup
(so for sure same kernel, as valgrind was just freshly compiled).
I'll try rebuilding and reinstalling world (even if it should not really
change, apart from version number); if something different happens I'll
report back.
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-unsubscr...@freebsd.org"
Re: devel/valgrind not working
On 3/5/19 4:43 PM, Serpent7776 wrote: 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? AFAICT there is no difference in userland between p8 and p9. p8 to p9 modification only affects kernel. 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-unsubscr...@freebsd.org"
Re: devel/valgrind not working
On Mon, 4 Mar 2019 17:27:45 +0100 Andrea Venturoli 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-unsubscr...@freebsd.org" -- /* * Serpent7776 */ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/valgrind not working
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? 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-unsubscr...@freebsd.org"
