lkml.org 
[lkml]   [2006]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
    In-Reply-To: <1157049193.22667.19.camel@dyn9047017100.beaverton.ibm.com>

    On Thu, 31 Aug 2006 11:33:13 -0700, Badari Pulavarty wrote:

    > 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()
    >
    > 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.

    --
    Chuck

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-09-01 12:21    [W:3.429 / U:0.700 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site