Looks like both logs were done on amd64 machines. Eclipse starts a new process on launch on that arch, which means that valgrind unfortunately didn't catch the error. You can force Eclipse to start the jvm in the same process instead of a new one by giving it the arguments "-vm /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/". If you use a jvm other than openjdk, replace the directory argument by the one containing libjvm.so for your preferred jvm.
So the commandline would look like this: G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --smc-check=all --log-file=valgrind.log /usr/bin/eclipse -vm /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/ -- Eclipse crashes on installing update https://bugs.launchpad.net/bugs/460104 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
