3 May
2012
3 May
'12
6:16 p.m.
On 05/03/2012 12:55 PM, Timothy Pearson wrote:
Tim, Doc, will do,
I should have more time this evening to work with valgrind. I have little
familiarity with it, so I'll just run it successively with the various tools and
post any output I get.
Any other tests you can think of, just let me know.
--
David C. Rankin, J.D.,P.E.
On 05/03/2012
07:38 AM, David C. Rankin wrote:
<snip>
I would use the default memchecker tool, as my initial guess would be
memory corruption based on the widely varied backtraces.
Tim
On 05/03/2012 01:53 AM, Mag. Dr. Nikolaus Klepp
wrote:
OK,
What tool in valgrind is the one we want? I tried cachegrind and that
didn't
produce anything: 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.