Feature-request:
Add backtrace to output for these warnings:
"Warning: set address range perms: large range
[0x4c339040, 0x206094130) (undefined)"
Explanation:
This was a large allocation which ate up all my memory when debugging
with valgrind making it hard for me to find where it happened.
The reason was an undefined integer in a class (uninitialized memory).
Valgrind only gives this one line warning (which is good), but
it would also be nice if it would give a backtrace for this...
Might have helped me to track down this bug sooner :)
--
With kind regards
Jonatan Wallmander
Vovoid Media Technologies AB
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
