mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.21-pre5 kksymoops for i386/ia64
Date: Tue, 18 Mar 2003 13:18:24 +1100	[thread overview]
Message-ID: <985.1047953904@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 18 Mar 2003 10:41:46 +1100." <30411.1047944506@ocs3.intra.ocs.com.au>

On Tue, 18 Mar 2003 10:41:46 +1100, 
Keith Owens <kaos@ocs.com.au> wrote:
>On Mon, 17 Mar 2003 17:33:07 +0100, 
>Andi Kleen <ak@muc.de> wrote:
>>Rather than using this patch I would rather backport the 2.5 code
>>which works fine even for cross and compresses the symbol tables too.
>
>The 2.5 kallsyms does not have section data which is required for kdb
>(and probably kgdb).  That data used to be there until Rusty deleted
>it, the lack of section data is one of the reasons that I no longer do
>kdb for 2.5.  If you want to kill kdb for 2.4 kernels as well, go ahead
>and backport the incomplete 2.5 code.

ps. The 2.5 kallsyms code is incompatible with modutils 2.4,
backporting the incomplete 2.5 kallsyms would only get debugging
symbols for the kernel, not for modules.  Changing modutils 2.4 is not
an option, I will not introduce an incompatible change in the middle of
a stable kernel series unless there is no choice (e.g. to fix a
critical bug).


  reply	other threads:[~2003-03-18  4:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26040.1047888163@kao2.melbourne.sgi.com.suse.lists.linux.kernel>
2003-03-17 16:33 ` Andi Kleen
2003-03-17 23:41   ` Keith Owens
2003-03-18  2:18     ` Keith Owens [this message]
2003-03-19 15:39       ` Andi Kleen
2003-03-19 22:17         ` Keith Owens
2003-03-19 22:34           ` Andi Kleen
2003-03-19 23:38         ` Keith Owens
2003-03-26 14:24           ` David Woodhouse
2003-03-17  8:02 Keith Owens
2003-03-17 15:20 ` David Woodhouse
2003-03-18  0:29   ` Keith Owens

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=985.1047953904@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®