Description Martin Oberhuber 2011-10-07 08:40:04 EDT

Build ID: Linuxtools-0.8.1 on RHEL5.3 x86_64 host
CQ:WIND00309298

When running the Massif tool from Eclipse, and the underlying valgrind process runs into a fatal error (such as out-of-memory), that fatal error is not properly reported in Eclipse. The valgrind commandline tool prints a nice and very verbose message when running out of memory, but the Eclipse tooling runs into an "EmptyStackError" instead.

This is confusing for end users and especially problematic when running valgrind on remote embedded targets, where main memory is often scarce - Valgrind does need an awful lot of main memory, so this use-case is relatively common. Not reporting the error is a major loss of functionality since as a user I can't understand what's the problem and how to address it so my original goal (valgrind profiling) can't be performed.

Expected behavior:
When the valgrind commandline process exits with a non-zero exitcode, logfile parsing should not be performed and the process output (stderr) should be shown to the end user such that they can understand the problem.

Steps to reproduce:
1. Limit maximum available virtual memory, e.g. by running this command in bash:
      ulimit -v 1024000
2. Launch Eclipse and import attached project
3. Build if not on x86_64 (binary is in the ZIP but rebuild may be needed)
4. Profile > Profile configurations.. and run the Massif Launch that's stored in
   the Project
   --> EmptyStackError is shown.
5. For reference / comparison, you can run the "mass.sh" shellscript on
   commandline, to see the commandline output. Or, in the Debug View show
   Properties of the Valgrind launch and copy-and-paste the commandline.