All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Rik Riel" <riel@redhat.com>, "Keith Owens" <kaos@sgi.com>
Cc: "Christoph Lameter" <christoph@lameter.com>,
	"Clyde Griffin" <CGRIFFIN@novell.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"jmerkey" <jmerkey@utah-nac.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Novell Linux Kernel Debugger (NLKD)
Date: Mon, 27 Jun 2005 08:46:12 +0200	[thread overview]
Message-ID: <42BFBCD4020000780001D7ED@emea1-mh.id2.novell.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506240801450.17151@chimarrao.boston.redhat.com>

>>> Rik Van Riel <riel@redhat.com> 24.06.05 14:02:16 >>>
>On Fri, 24 Jun 2005, Keith Owens wrote:
>
>> Which is misleading.  There is some backtrace code, under F12, where it 
>> is called Stack Trace.
>
>It's using function keys?   Do those work over serial console?

It's not "the" debugger that's using function keys. The console frontend (one of the two currently available agents) is, the serial interface (the other available agent) obviously isn't, but that one doesn't know about keys at all. The console one in turn isn't intended to be run over a serial console...

Jan


  reply	other threads:[~2005-06-27  7:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  7:38 Novell Linux Kernel Debugger (NLKD) Jan Beulich
2005-06-24  6:44 ` jmerkey
2005-06-24  8:26 ` Keith Owens
2005-06-24 12:02   ` Rik Van Riel
2005-06-27  6:46     ` Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 18:03 Clyde Griffin
2005-06-24  6:29 Jan Beulich
2005-06-23 22:54 Clyde Griffin
2005-06-23 21:14 ` Parag Warudkar
2005-06-23 23:43 ` Greg KH
2005-06-24  0:24 ` Christoph Lameter
2005-06-24  0:35   ` John W. Linville
2005-06-24  0:17     ` jmerkey
2005-06-24  1:56       ` Rik Van Riel
2005-06-24  0:31         ` jmerkey
2005-06-24  6:21       ` Jan Beulich
2005-06-24  4:59         ` jmerkey
2005-06-24 11:50           ` Chris Mason
2005-06-24 15:55             ` jmerkey
2005-06-24 18:16               ` Chris Mason
2005-06-24 17:15                 ` jmerkey
2005-06-24 19:29         ` Lee Revell
2005-06-24 19:49           ` Christoph Lameter
2005-06-24  0:46     ` Christoph Lameter
2005-06-24  1:36 ` Rik Van Riel
2005-06-24  2:15 ` Keith Owens
2005-06-27 18:14 ` Pavel Machek

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=42BFBCD4020000780001D7ED@emea1-mh.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=CGRIFFIN@novell.com \
    --cc=christoph@lameter.com \
    --cc=jmerkey@utah-nac.org \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=riel@redhat.com \
    /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.