On Wed, 28 Sep 2005, Lothar Werzinger wrote:
On Wednesday 28 September 2005 23:01, Aschwin Marsman wrote:
On Wed, 28 Sep 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.
This is not SUSE specific, please go to the http://valgrind.org/ website and under support you will find "Mailing Lists" and "Bug Reports"
Well it looks like SUSE picked a specific version of valgrind from the SVN repository and the guys from the valgrind team probably have no idea which one. So how can this be not SUSE specific? I would expect the SUSE team to look into the problem if they don't use a "release" of any software. In the best case they just file the bug report based on the version they took, right?
I don't know if you have a diamond support contract but I wouldn't expect SUSE to do this like you suggest for all packages that are available in their distribution. They would need an gigant staff to be able to do that, who would pay them? What I would do if I would have this problem is download the latest version (valgrind-3.0.1), build it, see if it gives the same problem and then report it. Off course I would look first if this is a known problem. valgrind is not an end user tool, I always want to use the latest version myself when I need it during software development.
Lothar
Good luck from the Netherlands, Aschwin Marsman -- aschwin@marsman.org http://www.marsman.org