On 05/03/2012 07:38 AM, David C. Rankin wrote: > On 05/03/2012 01:53 AM, Mag. Dr. Nikolaus Klepp wrote: >> This might be a stupid question, but did you try to run kwirte with valgrind? >> >> Nik > > There are no stupid questions when it comes to "did I do something?" The answer > is probably no... I'm a great monkey on this side of the keyboard, but I'm not a > career developer, so you guys that have ideas of what needs to be done, just ask > and I can carry it out on this end. I'll give valgrind a go and let you know as > well as the g++ command suggested by /dev/ammo42. > OK, What tool in valgrind is the one we want? I tried cachegrind and that didn't produce anything: 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? -- David C. Rankin, J.D.,P.E.