On Fri, 26 Mar 2004, Julie Wu wrote:
> 1. I ran into an error:
> 'Use of uninitialised value of size 4.'
> and the line number given pointing to an ending curly brace '}' of a
> 'void' function with no 'return' in the end. What is it complaining?
That likely corresponds to the instructions that tear down the stack frame
and do the return. Is it possible you accidentally trashed the return
value on the stack with a rubbish value, eg. by overrunning the end of a
stack array? Does the return go ok, or does it cause a crash?
> 2. I'm pretty sure all my object files are '-g' compiled. But some stack
> traces are of the form:
>
> ClassBar::FuncFoo(<binary_foo>: -1)
>
> The function name is extracted, but no file name ('ClassBar.cc') and line
> numbers, instead the binary name is present. Has any one seen this
> before?
Sounds like Valgrind can find the symbol tables, but not the debug info.
Are you absolutely sure you compiled with -g?
> 3. What's the difference between the 3 'low/medium/high' settings for the
> '--leak-resolution'? I remember seeing it some where, but could no longer
> locate it. :( Could someone kindly point me to the relevant doc section?
See manual section 3.2.
N
|