-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/12/12 04:40, Philippe Waroquiers wrote: > I think (not tested) that the below trivial change will keep the alloc > stack trace:
Tested and confirmed that it does (although the header printed says it was where freed). Thanks. > 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. This option if present would have saved me hours of work. In the end I only found the problem through sheer guesswork and luck. I will gladly trade as much memory as it takes in order to improve my productivity/reduce debug time. (I even run with the freelist set to several gigabytes because that will catch program shutdown problems with memory cycled at the beginning of the program run.) What will it take to get this into valgrind proper and the ability to show both free and alloc stacks? Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlDh8usACgkQmOOfHg372QSt+ACgx8N64p2QUjTg/JqhGBHXdWR0 338AniCc86KQD/z/+X/NugtB+QQmt03b =JUzs -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 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_122412 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
