From: slurn@griffin.engr.sgi.com (Scott Lurndal)
To: linux-kernel@vger.rutgers.edu
Cc: kdb@oss.sgi.com
Subject: [PATCH] kdb v1.0 for 2.3.29
Date: Tue, 1 Feb 2000 09:03:23 -0800 (PST) [thread overview]
Message-ID: <200002011703.JAA66461@griffin.engr.sgi.com> (raw)
I've placed a pre-release of kdb v1.0 (restructured to support
additional architectures) for ia32 on
http://oss.sgi.com/projects/kdb/download
--
This release restructures the code a bit and adds breakpoint
instruction style (int 03) breakpoints. They don't completely
work yet at this time, so as a workaround, the 'bph' command
which uses the hardware debug registers should be used to
establish breakpoints.
There is some debug code present to save and display the contents of the
last branch register MSR on page-fault entry to the kernel.
A list of changes and features can be found on
http://oss.sgi.com/projects/kdb/news.html
--
I'll be in NYC for linuxworld expo this week, so I won't be able
to move this forward to 2.3.41 until next week.
--
scott lurndal
sgi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-02-01 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200002011703.JAA66461@griffin.engr.sgi.com \
--to=slurn@griffin.engr.sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
/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
all inboxes | Powered by JetHome®