|
From: Philippe W. <phi...@sk...> - 2011-07-28 22:33:21
|
On Thu, 2011-07-28 at 23:50 +0200, Albert Strasheim wrote:
> Agreed. The segfault is a separate problem that has to be addressed.
You might try to compare how stacktraces are computed between
Valgrind core, Valgrind gdbserver, native gdb (cfr previous mail).
Alternatively, you might experiment by disabling various Valgrind JIT
optimisations e.g. using the options:
--vex-iropt-level=<0..2> [2]
--vex-iropt-precise-memory-exns=no|yes [no]
--vex-iropt-unroll-thresh=<0..400> [120]
--vex-guest-chase-thresh=<0..99> [10]
I think to disable as much as possible; you have to use respectively
0, yes, 0, 0.
Philippe
|