From: Andreas Schuldei <andreas@schuldei.org>
To: linux-kernel@vger.kernel.org
Subject: kdb against memory corruption?
Date: Sun, 6 Oct 2002 22:08:01 +0200 [thread overview]
Message-ID: <20021006200801.GD1316@lukas> (raw)
I think i found a case of memory corruption in the backport of
the linuxconsole-ruby patch to 2.4.19.
Some parts (not sure which yet) of the tty_struct get
overwritten. I do not yet know when that happens or how, but i
intend to find out with kdb and its bph brakepoint feature.
Unfortunatly my initial attempts to find the instance where the
memory segment gets corrupted failed. I specified a certain
address, a length of 4 byte and DATAW as arguments to the bph
command.
but reading the kdb manpage i get the impression that
startaddress and length have to match precisly:
DATAW Enters the kernel debugger when data of length
length is written to the specified address.
how can i use this to find the cause of the corruption? Anyone
done this before? i would want to be alerted whenever anything
withing a certain memory range gets overwritten.
next reply other threads:[~2002-10-06 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 20:08 Andreas Schuldei [this message]
2002-10-07 9:03 ` kdb against memory corruption? Keith Owens
2002-10-07 17:11 ` Andreas Schuldei
2002-10-07 22:51 ` Andreas Schuldei
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=20021006200801.GD1316@lukas \
--to=andreas@schuldei.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.