Oops stack trace missing function addresses

[Adrian Larumbe]

> OK, I'll bite.  You *are* getting the function name and offset, what additional
> knowledge do you get from knowing the VA?

I was hoping to use the VA to calculate the C source line where the
fault happens, by substracting the function's VA from the module load
address as revealed by cat /proc/modules, adding the offset within the
function and then passing the offset to addr2line.

I've just realised I might as well load the module object file into gdb
and do 'info line *(func+offset)'.

But how would I do this just with addr2line ?

> What architecture is this on?  Stack unwinding is architecture-dependent, so
> it may just be the unwinder for that arch doesn't output the virtual address.

It's a QEMU VM, 'uname -m' claims it's i686.