|
From: Lothar W. <lo...@tr...> - 2005-09-29 03:11:52
Attachments:
valgrind.log
|
I am using the RC1 on AMD64 and have problems with the valgrind (valgrind-3.0.1.SVN) there. It prints 'valgrind: the 'impossible' happened: Killed by fatal signal' and exits on my program. I attached the valgrind output. Lothar |
|
From: Julian S. <js...@ac...> - 2005-09-29 10:23:01
|
On Thursday 29 September 2005 03:26, Lothar Werzinger wrote: > I am using the RC1 on AMD64 and have problems with the valgrind > (valgrind-3.0.1.SVN) there. > > It prints 'valgrind: the 'impossible' happened: Killed by fatal signal' > and exits on my program. I attached the valgrind output. Hmm. Not sure what happened there. Can you try the current dev sources? svn co svn://svn.valgrind.org/valgrind/trunk cd trunk ./autogen.sh ./configure --prefix=... make install and see if it still happens? Handling of mmap etc has been completely changed recently and so it could be that this problem has already gone away. J |
|
From: Dennis L. <pla...@in...> - 2005-09-29 11:33:07
|
Hi, release date is on oct 6 so perhaps you should just wait these few days as there will be lots of changes to the SuSE Kernel and glibc/pthreads part of the system when released. greets Dennis At 04:26 29.09.2005, Lothar Werzinger wrote: >I am using the RC1 on AMD64 and have problems with the valgrind >(valgrind-3.0.1.SVN) there. > >It prints 'valgrind: the 'impossible' happened: Killed by fatal signal' and >exits on my program. I attached the valgrind output. > >Lothar Carpe quod tibi datum est |