public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, Andreas Schwab <schwab@suse.de>,
	Alan Modra <alan@linuxcare.com.au>,
	David Mosberger-Tang <davidm@hpl.hp.com>
Subject: Re: sched.c: why -fno-omit-frame-pointer?
Date: 20 Aug 2007 01:00:17 +0200	[thread overview]
Message-ID: <p73r6lz1666.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070819141732.GD32595@stusta.de>

Adrian Bunk <bunk@kernel.org> writes:
> 
> Is the -fno-omit-frame-pointer still required for some reason, or is 
> this a relict that could be removed?

It's needed so that the WCHAN /proc display can backtrace one
level up out of schedule()

-Andi

  parent reply	other threads:[~2007-08-19 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19 14:17 sched.c: why -fno-omit-frame-pointer? Adrian Bunk
2007-08-19 21:05 ` Arjan van de Ven
2007-08-19 23:00 ` Andi Kleen [this message]
2007-08-23 11:30   ` Ingo Molnar

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=p73r6lz1666.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=alan@linuxcare.com.au \
    --cc=bunk@kernel.org \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwab@suse.de \
    /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