If not yet done, upgrade to the last version of Valgrind (3.8.1).
Then use gdb+vgdb to connect to your application. For this, give
--vgdb-error=0 and follow the on-screen instructions.
I'm using SVN only releases. The docs don't build OK, so my manual didn't have
this info. I need to figure
Am 05.11.2012 01:49, schrieb Wonjoon Song:
Hello all,
In the lackey example, there is instrument function like
static VG_REGPARM(2) void trace_load(Addr addr, SizeT size).
Instead of calling this precompiled function, will I get performance gain if
I directly generate VEX code?
You will,
On Monday 05 November 2012 23:19:42 Philippe Waroquiers wrote:
On Mon, 2012-11-05 at 18:59 +0100, David Faure wrote:
The testcase http://www.davidfaure.fr/2012/qmutex_trylock.cpp
(from https://bugs.kde.org/show_bug.cgi?id=243232)
shows that an optimization inside Qt leads to a helgrind
With vgdb/gdb, the debugger hangs after a couple of continues.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00300b4ea3d7 in writev () from /lib64/libc.so.6
Is there a real 'int3' instruction there, or was SIGTRAP sent
from somewhere else [using kill()]? Look with something
On Tue, Nov 6, 2012 at 8:34 PM, John Reiser jrei...@bitwagon.com wrote:
With vgdb/gdb, the debugger hangs after a couple of continues.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00300b4ea3d7 in writev () from /lib64/libc.so.6
Is there a real 'int3' instruction there, or
On Tue, 2012-11-06 at 13:43 +0100, David Faure wrote:
On Monday 05 November 2012 23:19:42 Philippe Waroquiers wrote:
On Mon, 2012-11-05 at 18:59 +0100, David Faure wrote:
The testcase http://www.davidfaure.fr/2012/qmutex_trylock.cpp
(from https://bugs.kde.org/show_bug.cgi?id=243232)
