[Valgrind-users] Feature request - backtrace on "warning set address range perms"

[Jonatan W. <jo...@vo...>]

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