Skip to contentSkip to conversation

Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

DISCUSSION Chuck Ebbert 2 participants 2 messages Sep 1, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 16 lines · Badari Pulavarty

As you can see from the following stack - it shows

      msync_interval() -> 
              set_page_dirty() -> 
                      __set_page_dirty_buffers()

But actual trace is (looking at the code):

      msync_interval() -> 
              msync_page_range() ->
                 msync_pud_range() -> 
                    msync_pgd_range() ->
                       msync_pte_range() ->   
                              set_page_dirty() -> 
                                      __set_page_dirty_buffers()
Quoted 1 line

Why is it skipping all msync_page/pud/pgd/pte_range() routines ?

Sometimes this is caused by tail calls, i.e. when the last line of a function calls another function it can many times be optimized into a jump.

You can disable this by compiling with CONFIG_FRAME_POINTER=y.

Signature · 1 line
Chuck
#1 lore raw
Quoted 6 lines

Sometimes this is caused by tail calls, i.e. when the last line of a function calls another function it can many times be optimized into a jump.

You can disable this by compiling with CONFIG_FRAME_POINTER=y.

Even that will not disable automatic inlining, which is probably causing most of the missing frames here.

-Andi