> While strace is not prepared to do a full backtrace - could it
> recognize the vDSO and do a single frame? It should be pretty simple
> to recognize a canned code sequence and take a single action.
There are several different vDSO code sequences seen in different
configurations, different hardw
On Thu, Apr 23, 2009 at 01:39:56AM -0700, Roland McGrath wrote:
> The vDSO is a shared library provided by the kernel on some architectures.
> In x86-32 processes, the C library calls into this library to make a system
> call (__kernel_vsyscall). So it's the caller of that frame that is what is
>
> [...] i.e., you want a full stack backtrace. In
> modern systems, that requires interpreting (and having) unwind information
> (which you do have in the vDSO). strace is just prepared to do that.
^not
Sorry for the typo, and in case it got your
> I have a question regarding the ability of strace to print the
> instruction pointer where the syscall takes place. I'm trying to use
> this feature to trace a 32-bit process running on a amd64 gentoo
> system. Unfortunately, the eip values returned by strace don't make
> much sense:
I'm sorry y
