From: "Amit S. Kale" <akale@veritas.com>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gdb-serial.txt ?
Date: Thu, 26 Jul 2001 11:28:55 +0530 [thread overview]
Message-ID: <3B5FB19F.81B39ED1@veritas.com> (raw)
In-Reply-To: <3B5F3893.6030607@interactivesi.com>
Hi,
IFAIK gdb-serial.txt existed only in x86-kgdb
patch. It's still a part of the x86-kgdb patch.
You can also get the documenatation contained
in the file plus much more at
http://kgdb.sourceforge.net/.
Timur Tabi wrote:
>
> What happened to gdb-serial.txt? It's not in the Documentation/i386
> directory in the 2.4.2 kernel. Was it removed because 2.4 doesn't
> support serial gdb debugging?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Amit Kale
Veritas Software ( http://www.veritas.com )
prev parent reply other threads:[~2001-07-26 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 21:22 gdb-serial.txt ? Timur Tabi
2001-07-26 5:58 ` Amit S. Kale [this message]
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=3B5FB19F.81B39ED1@veritas.com \
--to=akale@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttabi@interactivesi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox