Hi,
On Sat, Mar 8, 2025 at 6:09 PM Landry Breuil wrote:
>
> hi,
>
> apparently valgrind is broken at runtime:
>
> $valgrind
> memcheck-amd64-openbsd[23142]: pinsyscalls addr 3806a478 code 20, pinoff
> 0x (pin 0 0-0 0) (libcpin 0 0-0 0) error 78
> Abort trap (core dumped)
Yes, valgrind is
From: Otto Moerbeek
Date: Tue, 17 Oct 2023 10:54:17 +0200
> On Tue, Oct 17, 2023 at 05:41:06PM +0900, Masato Asou wrote:
>
>> From: Otto Moerbeek
>> Date: Tue, 17 Oct 2023 07:52:12 +0200
>>
>> > On Tue, Oct 17, 2023 at 07:33:47AM +0900, Masato Asou wrote:
>> >
>> >> From: Masato Asou
>> >> D
On Tue, Oct 17, 2023 at 05:41:06PM +0900, Masato Asou wrote:
> From: Otto Moerbeek
> Date: Tue, 17 Oct 2023 07:52:12 +0200
>
> > On Tue, Oct 17, 2023 at 07:33:47AM +0900, Masato Asou wrote:
> >
> >> From: Masato Asou
> >> Date: Fri, 29 Sep 2023 19:39:12 +0900 (JST)
> >>
> >> ping
> >
> > Sor
From: Otto Moerbeek
Date: Tue, 17 Oct 2023 07:52:12 +0200
> On Tue, Oct 17, 2023 at 07:33:47AM +0900, Masato Asou wrote:
>
>> From: Masato Asou
>> Date: Fri, 29 Sep 2023 19:39:12 +0900 (JST)
>>
>> ping
>
> Sorry for not replying earlier.
No problem :-)
> The locations are reported
> correct
On Tue, Oct 17, 2023 at 07:33:47AM +0900, Masato Asou wrote:
> From: Masato Asou
> Date: Fri, 29 Sep 2023 19:39:12 +0900 (JST)
>
> ping
Sorry for not replying earlier. The locations are reported
correctly now. But there are spurious reports of accesses of a 8 byte
value on each system call. (te
From: Masato Asou
Date: Fri, 29 Sep 2023 19:39:12 +0900 (JST)
ping
> I have fixed the bug you reported when symbols were not printed.
>
> As shown below, if the lower 12 bits of Virtual Address are 0 and File
> Size is 0, then the a.out symbol will not be printed.
>
> $ readelf -l a.out
>
> P
I have fixed the bug you reported when symbols were not printed.
As shown below, if the lower 12 bits of Virtual Address are 0 and File
Size is 0, then the a.out symbol will not be printed.
$ readelf -l a.out
Program Headers:
Type Offset VirtAddr PhysAddr
On Tue, Sep 05, 2023 at 03:00:12PM +0900, Masato Asou wrote:
> From: Otto Moerbeek
> Date: Tue, 5 Sep 2023 07:40:18 +0200
>
> > On Tue, Sep 05, 2023 at 09:38:40AM +0900, Masato Asou wrote:
> >
> >> hi,
> >>
> >> I have fixed a bug in Valgrind. The Valgrind could not detect access
> >> outside
From: Otto Moerbeek
Date: Tue, 5 Sep 2023 07:40:18 +0200
> On Tue, Sep 05, 2023 at 09:38:40AM +0900, Masato Asou wrote:
>
>> hi,
>>
>> I have fixed a bug in Valgrind. The Valgrind could not detect access
>> outside the range of malloc.
>>
>> comments, ok?
>
> This works much better that befor
On Tue, Sep 05, 2023 at 09:38:40AM +0900, Masato Asou wrote:
> hi,
>
> I have fixed a bug in Valgrind. The Valgrind could not detect access
> outside the range of malloc.
>
> comments, ok?
This works much better that before. Thanks for working on this!
It now detects out of bounds read and wri
On Thu, Jul 13, 2023 at 10:05:53AM +0900, Masato Asou wrote:
> From: Masato Asou
> Date: Mon, 10 Jul 2023 08:05:16 +0900 (JST)
>
> > hi ports
> >
> > I made Valgrind 3.21.0 into a ports.
> >
> > In Valgrind 3.10.1 ports, some diffs were placed in
> > https://ftp.openbsd.org/pub/OpenBSD/distfile
From: Theo Buehler
Date: Sat, 8 Oct 2022 11:46:36 +0200
> There are still a few syscall numbers that are missing or not quite
> right. I'll need a bit of time to think about the rest of your diff.
>
> --- vki-scnums-openbsd.h Sat Oct 8 11:32:14 2022
> +++ syscall.h Sat Oct 8 11:46:11 2022
Let's leave uebayasi out of this.
On Sat, Oct 08, 2022 at 03:34:37PM +0900, Masato Asou wrote:
> From: Stefan Sperling
> Date: Fri, 7 Oct 2022 10:27:47 +0200
>
> > On Fri, Oct 07, 2022 at 02:37:15PM +0900, Masato Asou wrote:
> >> Hi tb and ports,
> >>
> >> I have adapted the system call number
From: Stefan Sperling
Date: Fri, 7 Oct 2022 10:27:47 +0200
> On Fri, Oct 07, 2022 at 02:37:15PM +0900, Masato Asou wrote:
>> Hi tb and ports,
>>
>> I have adapted the system call number definition to the new syscall.h
>>
>> comments, ok?
>
> Thank you!
>
> I have tried running devel/got in va
From: Stefan Sperling
Date: Fri, 7 Oct 2022 10:27:47 +0200
> On Fri, Oct 07, 2022 at 02:37:15PM +0900, Masato Asou wrote:
>> Hi tb and ports,
>>
>> I have adapted the system call number definition to the new syscall.h
>>
>> comments, ok?
>
> Thank you!
>
> I have tried running devel/got in va
On Fri, Oct 07, 2022 at 02:37:15PM +0900, Masato Asou wrote:
> Hi tb and ports,
>
> I have adapted the system call number definition to the new syscall.h
>
> comments, ok?
Thank you!
I have tried running devel/got in valgrind and it fails because
the __realpath syscall is missing. Could this be
Hi tb and ports,
I have adapted the system call number definition to the new syscall.h
comments, ok?
Index: Makefile
===
RCS file: /cvs/ports/devel/valgrind/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile
From: Otto Moerbeek
Subject: Re: valgrind
Date: Wed, 16 Dec 2020 20:27:58 +0100
> On Wed, Dec 16, 2020 at 09:33:43AM +0100, Otto Moerbeek wrote:
>
>> On Mon, Dec 14, 2020 at 02:24:52PM +0900, Masato Asou wrote:
>>
>> > Hi,
>> >
>> > From: Otto M
On Wed, Dec 16, 2020 at 09:33:43AM +0100, Otto Moerbeek wrote:
> On Mon, Dec 14, 2020 at 02:24:52PM +0900, Masato Asou wrote:
>
> > Hi,
> >
> > From: Otto Moerbeek
> > Date: Fri, 11 Dec 2020 08:54:36 +0100
> >
> > > Hi,
> > >
> > > I did some basic testing of valgrind on amd64 and it seems to
On Mon, Dec 14, 2020 at 02:24:52PM +0900, Masato Asou wrote:
> Hi,
>
> From: Otto Moerbeek
> Date: Fri, 11 Dec 2020 08:54:36 +0100
>
> > Hi,
> >
> > I did some basic testing of valgrind on amd64 and it seems to be in
> > better shape than before, at least for memory leak detection.
> >
> > Bu
Hi,
From: Otto Moerbeek
Date: Fri, 11 Dec 2020 08:54:36 +0100
> Hi,
>
> I did some basic testing of valgrind on amd64 and it seems to be in
> better shape than before, at least for memory leak detection.
>
> But I do seem to get a report on every syscall done. One example:
>
> ==7218== Use of
From: Martijn van Duren
Date: Mon, 14 Sep 2020 11:42:20 +0200
> On Mon, 2020-09-14 at 18:12 +0900, Masato Asou wrote:
>> Hi,
>>
>> From: Martijn van Duren
>> Date: Mon, 14 Sep 2020 10:43:28 +0200
>>
>> > I did some bisecting and it seems that the update to clang 10 broke
>> > valgrind. Specifi
On Mon, 2020-09-14 at 18:12 +0900, Masato Asou wrote:
> Hi,
>
> From: Martijn van Duren
> Date: Mon, 14 Sep 2020 10:43:28 +0200
>
> > I did some bisecting and it seems that the update to clang 10 broke
> > valgrind. Specifically /usr/local/lib/valgrind/memcheck-amd64-openbsd:
> >
> > $ ktrace -
Hi,
From: Martijn van Duren
Date: Mon, 14 Sep 2020 10:43:28 +0200
> I did some bisecting and it seems that the update to clang 10 broke
> valgrind. Specifically /usr/local/lib/valgrind/memcheck-amd64-openbsd:
>
> $ ktrace -i /usr/local/lib/valgrind/memcheck-amd64-openbsd
> Abort trap
> $ kdump
Sorry,
From: Masato Asou
Date: Mon, 09 Dec 2019 14:50:41 +0900 (JST)
> Valgrind does not run Pthread target program.
> I made patch to run Pthread target program.
I forget increment REVISION in Makefile.
--
ASOU Masato
oved files:
> devel/valgrind/patches:
>patch-coregrind_m_scheduler_scheduler_c
>patch-coregrind_pub_core_transtab_h
>
> Log message:
> Delete mmap(PROT_WRITE) from the memory area of the execution code of the
> target program.
From: Rafael Sadowski
Subject: Re
On Mon Oct 28, 2019 at 11:36:47AM +0900, Masato Asou wrote:
> From: Masato Asou
> Subject: Valgrind: Delete 'USE_WXNEEDED = Yes' from Makefile
> Date: Fri, 25 Oct 2019 16:40:43 +0900 (JST)
>
> > Hi ports,
> >
> > The Valgrind specifies 'READ | WRITE | EXEC' when allocating memory
> > for target
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
[ moved to ports@ ]
On 2017-05-25, Peter Ezetta wrote:
> Hello Misc,
>
> I have been trying to get Valgrind to run on OpenBSD 6.1-release, with
> all errata applied via syspatch(8), and I am having no luck. When
> executing Valgrind against any binary (or no binary at all), it claims to
> run out
Forgot to include ports in the reply. Forwarded below.
> On Saturday, July 9, 2016 11:57 AM, Thomas Frohwein
> wrote:
> >> On Saturday, July 9, 2016 11:41 AM, Stuart Henderson
> wrote:
>
>> > Have you tried it with an executable on /usr/local? cal (in /usr/bin)
> is not on
>> a wallow
Have you tried it with an executable on /usr/local? cal (in /usr/bin) is not on
a wallowed filesystem.
On 9 July 2016 16:29:23 BST, Thomas Frohwein wrote:
>
>
>
>Independent of executable or doas/su, valgrind fails with the following
>error message for me on -current:
>$valgrind cal
>valgrind:
On Thu, Dec 11, 2014 at 5:22 PM, Masao Uebayashi wrote:
> Reflected your comments + others from zhuk@. Especially, in DESCR, mention
> "valgrind-openbsd" page to report problems.
>
> Any explicit OK?
Looks good.
Ok with me, and thanks for your work on valgrind!
ciao,
David
> diff -Nru valgrind
Reflected your comments + others from zhuk@. Especially, in DESCR, mention
"valgrind-openbsd" page to report problems.
Any explicit OK?
diff -Nru valgrind.orig/Makefile valgrind/Makefile
--- valgrind.orig/Makefile Thu Dec 4 22:59:34 2014
+++ valgrind/Makefile Fri Dec 12 01:08:51 2014
@@
On 2014/12/11 16:24, Masao Uebayashi wrote:
> Here is the first attempt to port Valgrind to OpenBSD/amd64. Heavily based
> on that of FreeBSD.
>
> https://wiki.freebsd.org/Valgrind
> https://bitbucket.org/stass/valgrind-freebsd
I have a few minor tweaks,
>COMMENT = Ins
49 matches
Mail list logo
