Date: Wed, 1 Mar 2000 12:12:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: Check-Memory
In-Reply-To: <89go7u$i0e$1@nets3.rz.RWTH-Aachen.DE>
Message-ID: <Pine.SUN.3.91.1000301121101.12637I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 29 Feb 2000, Hans-Bernhard Broeker wrote:

> Triggered by this thread, I just had another look at Checker to
> refresh my memory about its actual working mechanism. Turned it does
> not even work on all kinds of Linux, any more (Checker is lacking
> behind, since 1998). It doesn't seem to work with glibc-2.1.

Thanks again for the info.  I understand that most of the work required 
to get Checker to work with DJGPP is to provide a Checker-compatible 
libc.  And I understand that this is also the major obstacle to its 
portability, since it requires so much of the underlying libc.