From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] debugging
Date: Fri, 7 Jan 2000 09:07:11 -0500 [thread overview]
Message-ID: <20000107140711.EEvvTqGnk04olSirw1V99MgPfZqV-gJwjKpuOwuwBOY@z> (raw)
The original usage of consdebug was just to give a hook into specialised
functions, usually during driver devlopment. That facility is still there,
but the default behaviour now is to drop into the remote debugger:
RDBFS(4) RDBFS(4)
NAME
rdbfs - remote kernel debugging file system
SYNOPSIS
rdbfs [ -d ] [ -p pid ] [ -t text ] [ device ]
DESCRIPTION
Rdbfs presents in /proc/pid (default /proc/1) a set of pro-
cess files for debugging a kernel over the serial line
device (default /dev/eia0).
The text file presented is just a copy of text (default
/386/9pc). It can usually be ignored, since the debuggers
open kernel files directly rather than using /proc/n/text.
Kernels can be remotely debugged only when they are sus-
pended and serving a textual debugging protocol over their
serial lines. Typing ``^t^td'' (control-t, control-t, d) at
the console will cause the kernel to enter this mode when it
`panics'. Typing ``^t^tD'' causes the kernel to enter this
mode immediately.
Because the debugging protocol is textual, a console pro-
vided by consolefs(4) may be substituted for the serial
device.
SOURCE
/sys/src/cmd/rdbfs.c
/sys/src/9/port/rdb.c
SEE ALSO
acid(1), db(1), consolefs(4)
Page 1 Plan 9 (printed 1/7/00)
next reply other threads:[~2000-01-07 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-07 14:07 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-07 0:37 David
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=20000107140711.EEvvTqGnk04olSirw1V99MgPfZqV-gJwjKpuOwuwBOY@z \
--to=jmk@plan9.bell-labs.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;
as well as URLs for NNTP newsgroup(s).