kdb
[Top] [All Lists]

Re: kdb and minicom

To: "Raj, Ashok" <ashok.raj@xxxxxxxxx>
Subject: Re: kdb and minicom
From: Keith Owens <kaos@xxxxxxx>
Date: Sat, 04 Oct 2003 12:09:04 +1000
Cc: kdb@xxxxxxxxxxx
In-reply-to: Your message of "Fri, 03 Oct 2003 10:00:51 MST." <A28EFEDC5416054BA1026D892753E9AFD06BE9@orsmsx404.jf.intel.com>
Sender: kdb-bounce@xxxxxxxxxxx
On Fri, 3 Oct 2003 10:00:51 -0700, 
"Raj, Ashok" <ashok.raj@xxxxxxxxx> wrote:
>Iam trying to use kdb with serial console on a IA64 box
>
>Iam using minicom to connect to the serial box from from another linux
>system.
>
>When we enter the break key, somehow minicom seems to eat that away, and
>not send it to the application... so iam not able to enter from the
>minicom session.

The term 'break key' is misleading, there is a real break key and there
is also a kdb break-in sequence which can be any set of characters, the
default for the kdb break-in code is control-A.  I am assuming that you
mean control-A to enter kdb.

Minicom uses control-A itself.  If you want to pass control-A through
minicom to the program you are talking to, press control-A twice.

Do not use control-A F for kdb.  That sends a real break code, which is
not what kdb uses.  As I say, the default kdb entry sequence is control-A
but that can be changed.  See kdb/kdbmain.c:kdb_serial_str for your kdb
entry key.

Heads up: control-A conflicts with gnu readline editting (start of line).
kdb v5.0 (WIP) will use <escape>KDB by default.

<Prev in Thread] Current Thread [Next in Thread>