Re: [Valgrind-users] Valgrind won't print the complete stacktrace if the bug is an unitialized argument to a function *written in assembly*

[Dirk M. <dm...@gm...>]

On Sunday 28 September 2003 15:42, Guilhem Bichot wrote:

> I thought this was of interest, if you sometimes can't get Valgrind to
> print the complete stacktrace. Maybe it can be classified as a feature
> request.

gdb does fairly complicated stuff to find the backtrace, and if even fails to 
print a stack trace then I believe that valgrind does not have much of a 
chance either. I believe the problem is that you didn't compile the assembler 
file with debug?

Is this inline assembler or a separate file? is it a .c file or a .S ? do you 
compile with -fomit-frame-pointer, or without? is it inline-assembly? if not, 
do you write the function prolog in assembler too? is objdump -d -S on the 
object file able to intermix source/code correctly?

I seem to remember that gdb has problems if it cannot find the function 
prolog.

any small testcase to look at?

> If you know a Valgrind option which would help, or any comment you
> have, they are warmly welcome :)

valgrind provides those superuseful CHECK_DEFINED macros :)