Sorry,
From: Stuart Henderson
Date: Fri, 18 Oct 2019 21:58:25 +0100
> On 2019/10/18 15:08, Masato Asou wrote:
>> From: YASUOKA Masahiko
>> Date: Wed, 02 Oct 2019 23:29:05 +0900 (JST)
>>
>> > I looked into the problem more.
>> >
>> > - unveil(2) itself fails
>> > - so file system related sys
From: Stuart Henderson
Subject: Re: valgrind diff to fix run memcheck on amd64
Date: Fri, 18 Oct 2019 21:58:25 +0100
> On 2019/10/18 15:08, Masato Asou wrote:
>> From: YASUOKA Masahiko
>> Date: Wed, 02 Oct 2019 23:29:05 +0900 (JST)
>>
>> > I looked into the proble
On 2019/10/18 15:08, Masato Asou wrote:
> From: YASUOKA Masahiko
> Date: Wed, 02 Oct 2019 23:29:05 +0900 (JST)
>
> > I looked into the problem more.
> >
> > - unveil(2) itself fails
> > - so file system related system calls are not restricted (yet)
> >
> > valgrind complains:
> >
> > ==13326
From: YASUOKA Masahiko
Date: Wed, 02 Oct 2019 23:29:05 +0900 (JST)
> I looked into the problem more.
>
> - unveil(2) itself fails
> - so file system related system calls are not restricted (yet)
>
> valgrind complains:
>
> ==13326==
> --13326-- WARNING: unhandled syscall: 114
> --13326-- You
Sorry, my delayed reply.
From: YASUOKA Masahiko
Date: Wed, 02 Oct 2019 23:29:05 +0900 (JST)
> I looked into the problem more.
>
> - unveil(2) itself fails
> - so file system related system calls are not restricted (yet)
>
> valgrind complains:
>
> ==13326==
> --13326-- WARNING: unhandled sy
YASUOKA Masahiko wrote:
> On Wed, 02 Oct 2019 08:35:26 -0600
> "Theo de Raadt" wrote:
> > YASUOKA Masahiko wrote:
> >> On Wed, 02 Oct 2019 07:24:46 -0600
> >> "Theo de Raadt" wrote:
> >> >> As far as my test (the log attached), valgrind seems to work with
> >> >> "pledge" but not work with "un
On Wed, 02 Oct 2019 08:35:26 -0600
"Theo de Raadt" wrote:
> YASUOKA Masahiko wrote:
>> On Wed, 02 Oct 2019 07:24:46 -0600
>> "Theo de Raadt" wrote:
>> >> As far as my test (the log attached), valgrind seems to work with
>> >> "pledge" but not work with "unveil".
>> >>
>> >> Is there any fundamen
YASUOKA Masahiko wrote:
> On Wed, 02 Oct 2019 07:24:46 -0600
> "Theo de Raadt" wrote:
> >> As far as my test (the log attached), valgrind seems to work with
> >> "pledge" but not work with "unveil".
> >>
> >> Is there any fundamental problem of valgrind to work with "pledge"?
> >
> > If unveil
On Wed, 02 Oct 2019 07:24:46 -0600
"Theo de Raadt" wrote:
>> As far as my test (the log attached), valgrind seems to work with
>> "pledge" but not work with "unveil".
>>
>> Is there any fundamental problem of valgrind to work with "pledge"?
>
> If unveil causes problems, then that means it is try
> As far as my test (the log attached), valgrind seems to work with
> "pledge" but not work with "unveil".
>
> Is there any fundamental problem of valgrind to work with "pledge"?
If unveil causes problems, then that means it is trying to access files.
unveil will return ENOENT or EACCES for files
Hi,
On Tue, 1 Oct 2019 16:15:51 +0100
Stuart Henderson wrote:
> On 2019/10/01 11:13, Kurt Mosiejczuk wrote:
>> Unfortunately on my test amd64 box, valgrind still just abort traps on
>> launch.
>>
>> eisenhower$ valgrind
>> Abort trap
>> eisenhower$ valgrind /bin/ls
>> Abort trap
>> eisenhower$ v
On Tue, 1 Oct 2019 11:32:36 -0400
Kurt Mosiejczuk wrote:
> On Tue, Oct 01, 2019 at 04:15:51PM +0100, Stuart Henderson wrote:
>> On 2019/10/01 11:13, Kurt Mosiejczuk wrote:
>> > Unfortunately on my test amd64 box, valgrind still just abort traps on
>> > launch.
>
>> > eisenhower$ valgrind
>> > Abo
Stuart Henderson 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
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/d
On Tue Oct 01, 2019 at 03:54:32PM +0900, Masato Asou wrote:
> From: Masato Asou
> Date: Fri, 27 Sep 2019 13:18:50 +0900 (JST)
>
> > Hi ports,
> >
> > This is a patch for running valgrind memcheck on amd64. I corrected
> > the following two problems.
> >
> > - FS register can be used.
> > -
From: Masato Asou
Date: Fri, 27 Sep 2019 13:18:50 +0900 (JST)
> Hi ports,
>
> This is a patch for running valgrind memcheck on amd64. I corrected
> the following two problems.
>
> - FS register can be used.
> - Fixed a problem that strip command rewrites offset and align of
> memcheck E
Hi ports,
This is a patch for running valgrind memcheck on amd64. I corrected
the following two problems.
- FS register can be used.
- Fixed a problem that strip command rewrites offset and align of
memcheck ELF file.
Index: Makefile
==
17 matches
Mail list logo