All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: New module loader makes kernel debugging much harder
Date: Sat, 23 Nov 2002 13:20:10 +1100	[thread overview]
Message-ID: <13542.1038018010@ocs3.intra.ocs.com.au> (raw)

The new module loader makes kernel debugging much harder.

There is no section information available, which means ...

* ksymoops cannot decode oops in modules.  Without section data, there
  is no way to reliably determine where module symbols were loaded.

* kgdb cannot debug modules.  gdb needs to know which modules are
  loaded and where each section of each module starts.

* kdb cannot display the section for a symbol.  Which means the user
  cannot do
    objdump -j <section_name> --adjust-vma=<start_address> module
  to map the code to the original object and source.

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.

Big step backwards, Rusty.


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  2:20 Keith Owens [this message]
2002-11-23  2:35 ` New module loader makes kernel debugging much harder John Levon
2002-11-23  2:43   ` Keith Owens
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=13542.1038018010@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.