Is this normal (i.e. known problem)?
~/felixvalgrind --tool=massif --stacks=yes ./ls
==264== Massif, a heap profiler
==264== Copyright (C) 2003-2010, and GNU GPL'd, by Nicholas Nethercote
==264== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info
==264== Command: ./ls
==264==
Hi
I'm currently debugging a program which uses lots of libraries and
sometimes, the backtrace size used by valgrind is too small... i.e. it
just shows 10 functions. Is there a way to see more than just that
(otherwize, I don't know which function of my code actually called the
code, which is
--num-callers=n
-Original Message-
From: Benjamin Schindler [mailto:bschind...@inf.ethz.ch]
Sent: Tuesday, January 18, 2011 5:59 PM
To: valgrind-users@lists.sourceforge.net
Subject: [Valgrind-users] Backtrace size
Hi
I'm currently debugging a program which uses lots of libraries and
Benjamin Schindler [mailto:bschind...@inf.ethz.ch] wrote:
... the backtrace size used by valgrind is too small... i.e. it
just shows 10 functions. Is there a way to see more than just that
Use the --num-callers=number command line switch.
best,
--
John Dallman
Parasolid Porting Engineer
A few things that might help you here:
1) Build your program with debugging information, which will help you to
understand exactly which line is causing a problem in your stack traces.
2) Tracking down uninitialized value warnings is much easier if you use the
--track-origins=yes option to
On 19/01/2011, at 5:58 AM, Dave Goodell wrote:
A few things that might help you here:
1) Build your program with debugging information, which will help you to
understand exactly which line is causing a problem in your stack traces.
Done.
2) Tracking down uninitialized value warnings is
