From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Badari Pulavarty <pbadari@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jan Beulich <jbeulich@novell.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Fri, 1 Sep 2006 12:21:36 +0200 [thread overview]
Message-ID: <200609011221.36718.ak@suse.de> (raw)
In-Reply-To: <200609010615_MC3-1-C9FA-ECE6@compuserve.com>
> 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
next prev parent reply other threads:[~2006-09-01 10:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 10:12 Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" Chuck Ebbert
2006-09-01 10:21 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-20 1:31 J. Bruce Fields
2006-08-21 6:48 ` Jan Beulich
2006-08-29 8:53 ` Was: " Borislav Petkov
2006-08-29 9:57 ` Jan Beulich
2006-08-29 11:01 ` Borislav Petkov
2006-08-29 11:08 ` Jan Beulich
2006-08-29 11:16 ` Andi Kleen
2006-08-29 13:00 ` Borislav Petkov
2006-08-29 14:36 ` Andi Kleen
2006-08-29 14:59 ` Borislav Petkov
2006-08-30 21:46 ` Badari Pulavarty
2006-08-31 7:35 ` Jan Beulich
2006-08-31 7:41 ` Andi Kleen
2006-08-31 7:48 ` Jan Beulich
2006-08-31 15:02 ` Badari Pulavarty
2006-08-31 15:16 ` Andi Kleen
2006-08-31 16:29 ` Badari Pulavarty
2006-08-31 18:11 ` Badari Pulavarty
2006-08-31 18:10 ` Andi Kleen
2006-08-31 18:33 ` Badari Pulavarty
2006-08-31 18:32 ` Andi Kleen
2006-09-06 6:31 ` Keith Owens
2006-09-06 7:43 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609011221.36718.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox