Re: [Valgrind-users] more information during a uninitialised memory error

[Nicholas N. <nj...@cs...>]

On Fri, 24 Feb 2006, smiley glitter wrote:

> When a uninitialised memory error is thrown supporting
> information like
>
> the address of the memory,
> the location of the memory (stack/heap/global)
> name of the function's stack frame (if stack)
> stack trace of the allocation (if heap)
> name of variable (if global)
>
> will be very very helpful to debug a complex
> application. Looking at the source code, I could see
> that the error->addr is a default "0" for value_error.
> Is this rendered impossible because of the translation
> ?

The problem is that the uninitialised value is in a register when this error 
is detected.  To give any of the above information Memcheck would have to 
know what memory location the value in the register came from.  This would 
be extra information to track for every single register value.  We've 
thought about this but can't think of a way to do it without causing 
horrendous slowdowns.  If anyone else can (it's more difficult than you 
might think) we'd like to hear about it.

Nick