linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brian Kuschak <bkuschak@yahoo.com>
To: "Daniel L. Taylor" <Dan.Taylor@atlp.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: debugging kernel modules
Date: Mon, 5 Aug 2002 19:43:22 -0700 (PDT)	[thread overview]
Message-ID: <20020806024322.41175.qmail@web40204.mail.yahoo.com> (raw)
In-Reply-To: <3D4F06D6.3646989D@atlp.com>


Thanks Dan, I think that's it.  With a little bit of
scripting I should be able to make it work nicely.


--- "Daniel L. Taylor" <Dan.Taylor@atlp.com> wrote:
> apropos modules -> lsmod; man lsmod -> ksyms;
> man ksyms -> "ksyms -m"
>
> Does this help?
>
> Brian Kuschak wrote:
> >
> > Wolfgang has a nice tutorial on this:
> > http://www.denx.de/doc/TQM8xxL/debugging.html
> >
> > But here's the question - is there any way to dump
> the
> > module load addresses, after the fact?  'insmod
> -m'
> > works well if you always remember to use it to
> load
> > the module.  FreeBSD has 'kldstat' which dumps
> module
> > address information at any time.  Is there
> anything
> > similar to kldstat for linux?  If not, any
> comments on
> > how hard it would be to write one?
> >
> > -Brian
> >
>
> --
> Dan.Taylor@atlp.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-08-06  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 23:00 debugging kernel modules Brian Kuschak
2002-08-05 23:14 ` Daniel L. Taylor
2002-08-06  2:43   ` Brian Kuschak [this message]
2002-08-06  4:31 ` Michael Habermann
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06  1:12 Ken Chou
2002-08-06  6:53 ` Wolfgang Denk
     [not found] <20020809010652.6470.qmail@web40201.mail.yahoo.com>
2002-08-09  7:15 ` Wolfgang Denk

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=20020806024322.41175.qmail@web40204.mail.yahoo.com \
    --to=bkuschak@yahoo.com \
    --cc=Dan.Taylor@atlp.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).