mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: New module loader makes kernel debugging much harder
Date: Sat, 23 Nov 2002 13:43:20 +1100	[thread overview]
Message-ID: <13864.1038019400@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 23 Nov 2002 02:35:13 -0000." <20021123023513.GC83190@compsoc.man.ac.uk>

On Sat, 23 Nov 2002 02:35:13 +0000, 
John Levon <levon@movementarian.org> wrote:
>On Sat, Nov 23, 2002 at 01:20:10PM +1100, Keith Owens wrote:
>
>> The complete lack of kernel and module symbols (no /proc/ksyms) means
>> that ksymoops is now useless on 2.5 kernels.  If you get an oops in a
>> kernel built without kksymoops, there is no way to decode the oops.
>
>Additionally, module profiling is not possible any more.
>
>> Big step backwards, Rusty.
>
>Somebody (this includes Rusty himself) needs to come up with a workable
>solution. For my own needs, the start address of the mapped module is
>good enough [snip]

Only if you assume that the .text is at a known offset from the start
of the module.  There are multiple programs that need to know where
each section really is, instead of making assumptions about how a
module is laid out.


  reply	other threads:[~2002-11-23  2:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  2:20 Keith Owens
2002-11-23  2:35 ` John Levon
2002-11-23  2:43   ` Keith Owens [this message]
2002-11-23 16:23     ` John Levon
2002-11-24  0:49       ` Keith Owens
2002-11-24  1:06         ` John Levon
2002-11-24  1:18           ` Keith Owens
2002-11-24  1:34             ` John Levon
2002-11-25  1:26             ` Rusty Russell
2002-11-23  4:22 ` Jamie Lokier

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=13864.1038019400@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --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®