All of lore.kernel.org
 help / color / mirror / Atom feed
From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How can I 'getchar()' in module code?
Date: Tue, 03 Dec 2013 15:20:55 +0100	[thread overview]
Message-ID: <1386080455.9055.28.camel@thorin> (raw)
In-Reply-To: <44408.1386077884@turing-police.cc.vt.edu>

On Die, 2013-12-03 at 08:38 -0500, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 03 Dec 2013 20:35:41 +0800,  said:
> > For debugging purpose, I want something like 'getchar()' that can pause
> > execution in the module code. Do any candidates I can choose?

You do not want that - there is way too much parallelism and
asynchronous stuff in the kernel.
Debugging with getchar() and the like pretty much works only in
single-threaded stuff ....

> The problem is that pausing execution in module code is dangerous, as if
> you hold any locks or anything like that, you can hang other threads or
> even the whole machine.
> 
> You probablhy want to be looking at the kgdb support, that is coded to
> work around a lot of the issues and you get full GDB support not just a
> getchar() pause.

Or just use printk() to print interesting values in interesting cases.

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd at petrovitsch.priv.at
                     LUGA : http://www.luga.at

  reply	other threads:[~2013-12-03 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 12:35 How can I 'getchar()' in module code? 乃宏周
2013-12-03 13:20 ` Daniel Baluta
2013-12-03 13:38 ` Valdis.Kletnieks at vt.edu
2013-12-03 14:20   ` Bernd Petrovitsch [this message]
2013-12-04 21:21     ` Daniel Baluta
2013-12-05 13:14       ` Bernd Petrovitsch
2013-12-05  1:34 ` Peter Teoh
2013-12-05  4:45   ` 乃宏周
2013-12-06  1:40 ` Fan Du

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=1386080455.9055.28.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --cc=kernelnewbies@lists.kernelnewbies.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.