rotten news relay - comp.unix.bsd.openbsd.misc - Re: valgrind => "Invalid write"

Subject: valgrind => "Invalid write"
From: Andrew Pennebaker
Newsgroups: comp.unix.bsd.openbsd.misc
Date: Fri, 9 Nov 2018 00:38 UTC

X-Received: by 2002:a24:7546:: with SMTP id y67-v6mr470931itc.26.1541723889758;
Thu, 08 Nov 2018 16:38:09 -0800 (PST)
X-Received: by 2002:a5b:b05:: with SMTP id z5-v6mr73442ybp.6.1541723889398;
Thu, 08 Nov 2018 16:38:09 -0800 (PST)
Newsgroups: comp.unix.bsd.openbsd.misc
Date: Thu, 8 Nov 2018 16:38:09 -0800 (PST)
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=70.226.12.99; posting-account=BgX_EAoAAADSgPfCTFtjxjxOSiJcIuzc
NNTP-Posting-Host: 70.226.12.99
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f46cd37b-0993-4e6a-9150-1163855b0e27@googlegroups.com>
Subject: valgrind => "Invalid write"
From: andrew.pennebaker@gmail.com (Andrew Pennebaker)
Injection-Date: Fri, 09 Nov 2018 00:38:09 +0000
Content-Type: text/plain; charset="UTF-8"
Path: eternal-september.org!news.eternal-september.org!reader01.eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!feed.ac-versailles.fr!proxad.net!feeder1-2.proxad.net!209.85.166.216.MISMATCH!g188-v6no1065088itg.0!news-out.google.com!n199-v6ni1498itn.0!nntp.google.com!z5-v6no1064705ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail

View all headers

Subject: Re: valgrind => "Invalid write"
From: Marc Espie
Newsgroups: comp.unix.bsd.openbsd.misc
Organization: Nerim -- xDSL Internet Provider
Date: Sat, 10 Nov 2018 10:35 UTC
References: 1

Path: eternal-september.org!news.eternal-september.org!reader01.eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!nerim.net!saria.nerim.net!not-for-mail
From: espie@lain.home (Marc Espie)
Newsgroups: comp.unix.bsd.openbsd.misc
Subject: Re: valgrind => "Invalid write"
Date: Sat, 10 Nov 2018 10:35:25 +0000 (UTC)
Organization: Nerim -- xDSL Internet Provider
Lines: 18
Message-ID: <ps6c9d$1dpk$1@saria.nerim.net>
References: <f46cd37b-0993-4e6a-9150-1163855b0e27@googlegroups.com>
NNTP-Posting-Host: espie.net8.nerim.net
X-Trace: saria.nerim.net 1541846125 46900 213.41.150.167 (10 Nov 2018 10:35:25 GMT)
X-Complaints-To: abuse@nerim.net
NNTP-Posting-Date: Sat, 10 Nov 2018 10:35:25 +0000 (UTC)
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: espie@lain.home (Marc Espie)

View all headers

In article <f46cd37b-0993-4e6a-9150-1163855b0e27@googlegroups.com>,
Andrew Pennebaker <andrew.pennebaker@gmail.com> wrote:
>I can valgrind my C/C++ apps in Debian, but when I try to run valgrind
>in OpenBSD, it complains "Invalid write" :/

It's possible the memory model is more strict.
It's also possible that valgrind does some things wrong.

Try running it on OpenBSD using strong malloc flags ? refer to malloc's
manpage. If you're running -current, it's now a sysctl, it used to be
a symlink called /etc/malloc.conf.

Setting it to "S" should help you debug things.

One big difference is that OpenBSD now has clang as default compiler.
And uses libc++ by default for C++ apps. Some sloppy stuff you're doing
might not agree with that...

Good news. Ten weeks from Friday will be a pretty good day.

comp / comp.unix.bsd.openbsd.misc / Re: valgrind => "Invalid write"

Subject	Author
valgrind => "Invalid write"	Andrew Pennebaker
Re: valgrind => "Invalid write"	Marc Espie