On Wednesday 08 October 2008, Yuri wrote: > I debug an application and need to know which function calls were made. > Many function though not inlined have optimized away epilogs, replaced > by a jump. > And google-perftools tool for example doesn't pick such functions up. > > Is there an option in gcc forcing it to emit full prologs/epilogs even > for optimized code? I'm not sure, but I think tools such as google-perftools look at the stack frames, which make the option '-fno-omit-frame-pointer' your first pick. You can also try '-mprologue-epilogue'. Check the gcc manual or the info pages for more 'debugging-friendly' options. -- Mihai Donțu unices.bitdefender.com
