From: gshan <gshan@alcatel-lucent.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to access kdb explicitly
Date: Fri, 01 Jun 2007 16:44:07 +0800 [thread overview]
Message-ID: <465FDC57.6000800@alcatel-lucent.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706011042320.29896@twin.jikos.cz>
Jiri Kosina wrote:
> On Fri, 1 Jun 2007, gshan wrote:
>
>
>> I want to access kdb explicitly. For example, I could recognize the
>> special characters inside console driver. If the the special characters
>> are detected , then drop to kdb immediately. However, I don't know what
>> should I to do after the special characters received.
>>
>
> See http://www.ibm.com/developerworks/linux/library/l-kdbug/ - section
> "Activating KDB".
>
>
Thanks a lot :-)
next prev parent reply other threads:[~2007-06-01 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 7:19 Callchain contains impossible call George Krajcsovits
2007-06-01 7:25 ` How to access kdb explicitly gshan
2007-06-01 8:42 ` Jiri Kosina
2007-06-01 8:44 ` gshan [this message]
2007-06-01 10:33 ` Callchain contains impossible call Miklos Szeredi
2007-06-01 11:32 ` Andi Kleen
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=465FDC57.6000800@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=jikos@jikos.cz \
--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