linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schuldei <andreas@schuldei.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Keith Owens <kaos@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: kdb against memory corruption?
Date: Tue, 8 Oct 2002 00:51:16 +0200	[thread overview]
Message-ID: <20021007225116.GF1102@lukas> (raw)
In-Reply-To: <20021007171140.GD1102@lukas>

* Andreas Schuldei (andreas@schuldei.org) [021007 19:11]:
> an other idea (by erikm) was that virutal and physical address
> mode is mixed up. how do i find out which one is used by kdb and the
> debug interface of the cpu? do i need to convert, somehow?

yet another possibility is that a 3Dnow function is used for
memset. Would that be caught?

i tried compiling the kernel for i386, but it still did not work
(to be droped into kdb when the memory gets currupted).

      reply	other threads:[~2002-10-07 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06 20:08 kdb against memory corruption? Andreas Schuldei
2002-10-07  9:03 ` Keith Owens
2002-10-07 17:11   ` Andreas Schuldei
2002-10-07 22:51     ` Andreas Schuldei [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=20021007225116.GF1102@lukas \
    --to=andreas@schuldei.org \
    --cc=kaos@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;
as well as URLs for NNTP newsgroup(s).