Date: Sun, 6 Oct 2002 22:08:01 +0200
From: Andreas Schuldei <andreas@schuldei.org>
To: linux-kernel@vger.kernel.org
Subject: kdb against memory corruption?
Message-ID: <20021006200801.GD1316@lukas>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1112
Lines: 26

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/