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
hi,
I have fixed a bug in Valgrind. The Valgrind could not detect access
outside the range of malloc.
comments, ok?
--
ASOU Masato
Index: devel/valgrind/Makefile
===
RCS file: /cvs/ports/devel/valgrind/Makefile,v
retrieving revision
10 matches
Mail list logo