[lkml]   [2012]   [Feb]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC 0/5] kernel: backtrace unwind support
On Fri, Feb 10, 2012 at 11:27 AM, Arnaldo Carvalho de Melo
<> wrote:
> "Vote for --fno-omit-frame-pointer! One register is a cheap price to pay
> for not going insane!"
> /me goes back to non political things.

Even with -fomit-frame-pointer (which seems to be a big deal on Atom
in particular), the call frames really don't look that horrible even
when we guess. And seeing the occasional stale pointer can often give
hints about what the thing was doing before, so it's not even

The biggest problem actually seems to often be some gcc versions that
allocate a *lot* of stack space for some functions and then never
really use it. That ends up then letting *tons* of really old stale
code pointers "shine through".

Sometimes it's our code that just has horrible stack usage with crazy
worst-case allocations or something. We've fixed a few of them, it
seems to be getting better.


 \ /
  Last update: 2012-02-10 20:35    [W:0.067 / U:11.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site