3 May
2012
3 May
'12
3:31 p.m.
08:09 valkyrie:~> valgrind --tool=cachegrind
kwrite
==1042== Cachegrind, a cache and branch-prediction profiler
==1042== Copyright (C) 2002-2011, and GNU GPL'd, by Nicholas Nethercote et
al. ==1042== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright
info ==1042== Command: kwrite
==1042==
Killed
The strange thing was I could open long files in kwrite and cursor down
without a crash when running in valgrind. However, pasting until the line
wrapped caused the crash as normal. Let me know what the valgrind command
line should look like. Or, is trying to run valgrind in virtualbox not
going to work to begin with?
Could you try "helgrind" as a tool? What you see is most likely a crash in an
other thread.
I usually work my way through all tools that in valgrind, beginning with
memcheck (the default), then helgring, callgrind ... simply down the list
http://www.valgrind.org/docs/manual/manual.html - and I do not use virtualbox
for debugging (but I don't know if it matters).
Nik