I tried the testcase provided on kde's bug repport, and it is still working
on my machine:
w...@celine:~/debian-fix/valgrind-test% valgrind ./mremap_test
==2811== Memcheck, a memory error detector
==2811== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==2811== Using Valgrind-3.5.0
I fail to reproduce it with minimal testcases. Though it is known
upstream:
https://bugs.kde.org/show_bug.cgi?id=204484
I have very similar backtraces here.
On Sun, Feb 14, 2010 at 12:51:10PM +0100, Moritz Muehlenhoff wrote:
> On Sat, Jan 30, 2010 at 04:12:18PM -0500, Jean-Baptiste Wons wrote:
>
On Sat, Jan 30, 2010 at 04:12:18PM -0500, Jean-Baptiste Wons wrote:
[Adding Pierre to CC]
> Package: valgrind
> Severity: normal
>
> I tried on version 1:3.5.0-3, and it does work for me.
>
> This is my test program:
> #define _GNU_SOURCE
> #include
> #include
> #include
>
> int main()
> {
Package: valgrind
Severity: normal
I tried on version 1:3.5.0-3, and it does work for me.
This is my test program:
#define _GNU_SOURCE
#include
#include
#include
int main()
{
void *someMem = malloc(1);
void *aligned = (void*)((long)someMem & ~4095L);
((char*)aligned)[1000] =
4 matches
Mail list logo