public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] kdb v1.8a-2.4.5-ia64-010626
Date: Thu, 28 Jun 2001 00:05:27 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005793@msgid-missing> (raw)

On Wed, 27 Jun 2001 00:09:08 -0700, 
David Mosberger <davidm@hpl.hp.com> wrote:
>The latest IA-64 patch is available at:
> ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/
>in file linux-2.4.5-ia64-010626.diff*.

kdb-v1.8a-2.4.5-ia64-010626 is available in
ftp://oss.sgi.com/projects/kdb/download/ia64.

kdb is being upgraded with some new features for better automatic bug
reporting, this is a partial release, hence 1.8a.

The major change from 1.8 to 1.8a is the addition of longjmp() support
for kdb.  The LINES parameter is now honoured so you can quit out of a
long set of output, set LINES=0 to get no paging.  The big advantage of
longjmp() support is that kdb can now attempt to recover from internal
errors, including bad addresses.  See also variable RECURSE in
Documentation/kdb/kdb.mm.



                 reply	other threads:[~2001-06-28  0:05 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=marc-linux-ia64-105590693005793@msgid-missing \
    --to=kaos@melbourne.sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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