mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nikhil Bhargava" <nikhilbhargav_nsit@coolgoose.com>
To: linux-kernel@vger.kernel.org
Subject: options to debug drivers in form of loadable modules
Date: Mon, 14 Feb 2005 18:50:10 +0550	[thread overview]
Message-ID: <1108387210.143301299@as03.coolgoose.com> (raw)

hi all,

I am looking for ways to debug those device drivers that have been written as loadable modules 
and loaded on fly and not complied with kernel. Using printks do help and looing at debug 
messages also help but at time of crach during development, its very difficult to find the exact 
location of crash. 

Any pointers or suggestions


Thanks,

nikhil bhargava

                 reply	other threads:[~2005-02-14 13:20 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=1108387210.143301299@as03.coolgoose.com \
    --to=nikhilbhargav_nsit@coolgoose.com \
    --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®