Re: [Libunwind-devel] different stack trace results for direct syscall and libc

[Arun Sharma]

On Mon, Feb 8, 2010 at 6:30 AM, Tanya Gornak <address@hidden> wrote:

but when it happend in wirte function I get call stack which contained only main function: 

00000000b804e424 +0xbfef0f18                      (sp=00000000bf87281c)                                

0000000008048504 main+0xb                         (sp=00000000bf872860)                                             

00000000b7f14b86 __libc_start_main+0xe6           (sp=00000000bf872870)                                              

00000000080483e1 _start+0x21                      (sp=00000000bf8728f0)       

Is it possible that your compiler inlined f() and g() into main in one case, but not the other? gcc also does tail call optimization, so some calls might be converted into jumps.

 -Arun