On Mon, 2012-12-31 at 12:17 -0800, Roger Binns wrote: > > It might be a good idea to have a new memcheck option > > --keep-alloc-stacktrace=yes|no and/or to allow to (optionally) remember > > and report the alloc stack trace in addition to the "free" stack > > trace. This will however imply (for a 64 bits platform) 8 bytes more > > per allocated block.
> What will it take to get this into valgrind proper and the ability to show > both free and alloc stacks? I think it would not be very difficult. Not too clear if we just need the option: --keep-alloc-stacktrace=yes|no remember alloc stack trace for freed blocks [no] or if we better have something like: --keep-alloc-stacktrace=yes|until-freed|no [until-freed] --keep-free-stacktrace=yes|no [yes] or maybe --keep-stacktraces=alloc|free|alloc-and-free|alloc-else-free|none [alloc-else-free] (default values in [] brackets are backward compatible with current behaviour). Philippe ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
