valgrind crashes on memcheck for a given program

[Albert Vilella]

Binary package hint: valgrind

run valgrind memcheck for a given program causes a crash

[D3m0n1q_733rz (cryo-rebirth)]

Yeah, what they said...Ran it with Alleyoop to find memory leaks in liquidwar (25 of them by the way) and it crashed.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Martin Olsson (mnemo)]

Daniel,

I still get SIGSEGV in memcheck when analysing pretty much _any_ program using valgrind on a x64 with intrepid. Upstream says valgrind should be working on x64 so this is likely an ubuntu bug and not a general valgrind bug.

The specific crash I am seeing is the exact one that D3m0n1q_733rz report about above, i.e. a crash in do_syscall_WR.

My auto submitted crash report is here:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/278542

I found found another duplicate of my bug here:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/162933

And of course my bug report closed as a duplicate of a third report (bug id 208120) however this bug is not accessible by the community.

I think getting valgrind to work on intrepid/x64 should be fairly high priority seeing as how valgrind is used for finding and analyzing many other bugs.

[Dimitrios Symeonidis (azimout)]

switching back to new

[xteejx (xteejx)]

Does this error occur in Jaunty? Would it be possible to try and reproduce this in Jaunty? If so can you enable apport by typing "sudo force_start=1 /etc/init.d/apport restart" (without quotes). Thank you.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!