From: Keith Owens <kaos@ocs.com.au>
To: LA Walsh <law@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: odd memory corrupt problem
Date: Fri, 23 Feb 2001 14:27:09 +1100 [thread overview]
Message-ID: <1256.982898829@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 22 Feb 2001 18:46:24 -0800." <3A95CF00.4C8A3EBE@sgi.com>
On Thu, 22 Feb 2001 18:46:24 -0800,
LA Walsh <law@sgi.com> wrote:
>Any ideas why? Not that I'm whining, but a good debugger with a 'watch' capability
>would do wonders at this point.
kdb - bpha audit_state dataw
prev parent reply other threads:[~2001-02-23 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 2:46 odd memory corrupt problem LA Walsh
2001-02-23 3:27 ` Keith Owens [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=1256.982898829@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=law@sgi.com \
--cc=linux-kernel@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