mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	Jan Beulich <jbeulich@novell.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Martin Bligh <mbligh@google.com>
Subject: Re: 2.6.17-rc2-mm1
Date: Thu, 4 May 2006 02:22:48 -0400	[thread overview]
Message-ID: <200605040224_MC3-1-BEC3-2856@compuserve.com> (raw)

In-Reply-To: <445903DD.6090408@shadowen.org>

On Wed, 03 May 2006 20:26:21 +0100, Andy Whitcroft wrote:

>        <ffffffff8047c8e8>{__sched_text_start+1856} <EOE>new stack 0 (0 0
> 10046 10 ffffffff8047c8e8)

Wow.  The extra debug patch yields... exactly the same address that's
already being printed.

The real problem is that the stack-dump code prints the wrong symbol
name here.  I don't see any easy way to fix it other than to put some
filler at __sched_text_start so the first sched function has a unique
address.


-- 
Chuck
"Penguins don't come from next door, they come from the Antarctic!"


             reply	other threads:[~2006-05-04  6:27 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  6:22 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03  5:37 2.6.17-rc2-mm1 Chuck Ebbert
     [not found] <4450F5AD.9030200@google.com>
2006-04-28  8:20 ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 14:24   ` 2.6.17-rc2-mm1 Martin J. Bligh
2006-05-01 17:07     ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 17:14       ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:19       ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:26         ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:55           ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:57             ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 18:32               ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-01 23:29                 ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:32       ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-02 20:20         ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 18:34     ` 2.6.17-rc2-mm1 Andi Kleen
2006-05-02 13:20       ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-02 20:00       ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-02 20:09         ` 2.6.17-rc2-mm1 Andi Kleen
2006-05-03  6:47           ` 2.6.17-rc2-mm1 Jan Beulich
2006-05-03  6:49             ` 2.6.17-rc2-mm1 Andi Kleen
2006-05-03  7:08               ` 2.6.17-rc2-mm1 Jan Beulich
2006-05-03  7:38                 ` 2.6.17-rc2-mm1 Andi Kleen
2006-05-03  8:12                   ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-03  8:25                     ` 2.6.17-rc2-mm1 Jan Beulich
2006-05-03 19:26               ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-04  7:40                 ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-04 16:28                 ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-04-27 16:54 2.6.17-rc2-mm1 Martin Bligh
2006-04-27  8:41 2.6.17-rc2-mm1 Andrew Morton
2006-04-27 10:16 ` 2.6.17-rc2-mm1 Andi Kleen
2006-04-27 19:19   ` 2.6.17-rc2-mm1 Andrew Morton
2006-04-27 19:26     ` 2.6.17-rc2-mm1 Andi Kleen
2006-04-27 21:41     ` 2.6.17-rc2-mm1 Grant Coady
2006-04-27 21:50       ` 2.6.17-rc2-mm1 Randy.Dunlap
2006-04-27 22:16         ` 2.6.17-rc2-mm1 Andrew Morton
2006-04-27 10:27 ` 2.6.17-rc2-mm1 Michal Piotrowski
2006-04-27 13:07   ` 2.6.17-rc2-mm1 Michal Piotrowski
2006-04-27 15:28     ` 2.6.17-rc2-mm1 Greg KH
2006-04-27 15:32       ` 2.6.17-rc2-mm1 Michal Piotrowski
2006-04-27 20:53         ` 2.6.17-rc2-mm1 Greg KH
2006-04-27 22:09           ` 2.6.17-rc2-mm1 Michal Piotrowski
2006-04-27 15:26   ` 2.6.17-rc2-mm1 Greg KH
2006-04-27 15:43     ` 2.6.17-rc2-mm1 Michal Piotrowski
2006-04-27 15:47 ` 2.6.17-rc2-mm1 Matthieu CASTET
2006-04-27 18:02   ` 2.6.17-rc2-mm1 Vivek Goyal
2006-04-27 23:24     ` 2.6.17-rc2-mm1 Greg KH
2006-04-28 14:40       ` 2.6.17-rc2-mm1 Vivek Goyal
2006-04-28 16:07     ` 2.6.17-rc2-mm1 matthieu castet
2006-04-28 18:05       ` 2.6.17-rc2-mm1 Vivek Goyal

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=200605040224_MC3-1-BEC3-2856@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@google.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

Powered by JetHome