public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: gjertsen@us.ibm.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] info on kernel module debugging
Date: Thu, 05 Oct 2000 19:45:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205549@msgid-missing> (raw)


I need to be able to step through some of our kernel module code
at the assembly level, but it doesn't appear that I can do this while
running on a "real" IA64 box.
I am fairly sure that the problem I am encountering is not a bug in
our code (yeah ... trust me), but I can't isolate the root cause right now
because the machine just plain old freezes on me.

Answers to the following questions would help though:

1) I've tried using kdb to set breakpoints at kernel module functions
that were exported and this doesn't seem to work. I end up
getting a kernel oops and complaint about being unable to
handle the paging request. It appears to be stopping/panicking right
before I want it to, though, and kdb was willing to set a bp there. :)
Should I be able to do this or not?
I see that kdb works fine when I set up break points for
functions in the kernel itself. (I'm currently using turbolinux test8
kernel).

2) Is there any sort of approx. timeline for when the remote kernel
debugger
will be available for IA64 (kgdb)?

3) Does the magic system request key work on this platform? I've tried it
out with
no luck and my autoconf file indicates CONFIG_MAGIC_SYSRQ is enabled.
Something else I need to be doing here?

Thanks for any pointers,

--Rob




                 reply	other threads:[~2000-10-05 19:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590678205549@msgid-missing \
    --to=gjertsen@us.ibm.com \
    --cc=linux-ia64@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