Tuesday, October 01, 2019

Re: valgrind diff to fix run memcheck on amd64

Stuart Henderson <stu@spacehopper.org> wrote:

> On 2019/10/01 11:13, Kurt Mosiejczuk wrote:
> > On Tue, Oct 01, 2019 at 12:42:18PM +0200, Rafael Sadowski wrote:
> > > On Tue Oct 01, 2019 at 03:54:32PM +0900, Masato Asou wrote:
> >
> > > > Additional information:
> >
> > > > - Abort trap was occurred when lounched valgrind.
> >
> > > > $ cd /usr/ports/devel/valgrind
> > > > $ make && doas make install
> > > > $ valgrind /bin/ls
> > > > Abort trap
> > > > $
> >
> > > > Sorry, I lost --strip-all option into
> > > > coregrind/link_tool_exe_openbsd.in.
> >
> > > > New patch is below:
> >
> > > Thanks Masato Asou
> >
> > > I can confirm this patch fixes valgrind on amd64. I'm not in the
> > > position to evaluate the quality of the patch, however it unbreaks
> > > valgrind for me.
> >
> > > RS
> >
> > Unfortunately on my test amd64 box, valgrind still just abort traps on
> > launch.
> >
> > eisenhower$ valgrind
> > Abort trap
> > eisenhower$ valgrind /bin/ls
> > Abort trap
> > eisenhower$ valgrind python2.7
> > Abort trap
> > eisenhower$ valgrind python3.7
> > Abort trap
> > eisenhower$ valgrind /bin/true
> > Abort trap
> > eisenhower$
>
> Not sure about the pythons, but most things in base won't work due to pledge

Which is a good thing. valgrind wants to do too much.

No comments:

Post a Comment