|
From: Bob R. <bo...@br...> - 2012-06-20 20:11:03
|
Hi, I'm using valgrind with a C++ program that embeds python. The stack trace is pretty deep, greater than 50 at almost every point valgrind finds a memory leak. Unfortunately, I can't see the stack frame that started this chain because 50 is not enough. Is there a way to increase this limit? Thanks, Bob |
|
From: Philippe W. <phi...@sk...> - 2012-06-20 20:58:26
|
On Wed, 2012-06-20 at 16:09 -0400, Bob Rossi wrote: > Hi, > > I'm using valgrind with a C++ program that embeds python. > > The stack trace is pretty deep, greater than 50 at almost every > point valgrind finds a memory leak. > > Unfortunately, I can't see the stack frame that started this > chain because 50 is not enough. > > Is there a way to increase this limit? It should be enough (this is theory, untested) to change the below in coregrind/pub_core_execontext.h and recompile. /* The maximum number of calls we're prepared to save in an ExeContext. */ #define VG_DEEPEST_BACKTRACE 50 |