|
From: David G. <dav...@gm...> - 2011-07-18 00:50:21
|
Hi! I'm using a modified version of lackey so that I print the access made by superblocks in a specific way. I'm tracking the function calls to a specific group of functions but I can't do it if the level of function calls gets too deep. I've tried using the --num-callers setting it to 16 and above (from what I've read 12 is the default) but I still can't track it... I'm able to track it if the level isn't too deep... Am I doing something wrong? I'm using the vg-in-place script to run the tests. David |
|
From: Josef W. <Jos...@gm...> - 2011-07-18 18:37:55
|
On Monday 18 July 2011, David Granchinho wrote: > Hi! I'm using a modified version of lackey so that I print the access > made by superblocks in a specific way. I'm tracking the function calls > to a specific group of functions but I can't do it if the level of > function calls gets too deep. I've tried using the --num-callers > setting it to 16 and above (from what I've read 12 is the default) but > I still can't track it... Not sure what you are actually doing, and how option "--num-callers" is relevant; that is used as the size of a stack trace retrieved e.g. with VG_(record_ExeContext). Can you show us your relevant changes to lackey? Josef > I'm able to track it if the level isn't too > deep... Am I doing something wrong? > I'm using the vg-in-place script to run the tests. > > David > > ------------------------------------------------------------------------------ > AppSumo Presents a FREE Video for the SourceForge Community by Eric > Ries, the creator of the Lean Startup Methodology on "Lean Startup > Secrets Revealed." This video shows you how to validate your ideas, > optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: David G. <dav...@gm...> - 2011-07-18 21:50:37
|
Hi! Thank you for the reply! But it was my mistake and I assumed this was the problem. Upon further investigation I realized that this was not the source of the problem and I managed to solve it. Thank you! 2011/7/18 Josef Weidendorfer <Jos...@gm...>: > On Monday 18 July 2011, David Granchinho wrote: >> Hi! I'm using a modified version of lackey so that I print the access >> made by superblocks in a specific way. I'm tracking the function calls >> to a specific group of functions but I can't do it if the level of >> function calls gets too deep. I've tried using the --num-callers >> setting it to 16 and above (from what I've read 12 is the default) but >> I still can't track it... > > Not sure what you are actually doing, and how option "--num-callers" is > relevant; that is used as the size of a stack trace retrieved > e.g. with VG_(record_ExeContext). > Can you show us your relevant changes to lackey? > > Josef > >> I'm able to track it if the level isn't too >> deep... Am I doing something wrong? >> I'm using the vg-in-place script to run the tests. >> >> David >> >> ------------------------------------------------------------------------------ >> AppSumo Presents a FREE Video for the SourceForge Community by Eric >> Ries, the creator of the Lean Startup Methodology on "Lean Startup >> Secrets Revealed." This video shows you how to validate your ideas, >> optimize your ideas and identify your business strategy. >> http://p.sf.net/sfu/appsumosfdev2dev >> _______________________________________________ >> Valgrind-users mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-users >> > > > |