Date: Wed, 18 Sep 2002 23:51:11 +0200
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: The Bat! (v1.61) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <517872820.20020918235111@softhome.net>
To: AYeryomin AT excelsior-usa DOT com (Alex Yeryomin)
CC: djgpp AT delorie DOT com
Subject: Re: Memory Supervision System cannot be compiled
In-Reply-To: <96eb2770.0209180650.27bf5939@posting.google.com>
References: <96eb2770 DOT 0209180650 DOT 27bf5939 AT posting DOT google DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Sep 2002 21:58:56.0992 (UTC) FILETIME=[961E2E00:01C25F5E]
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Hello everybody,

> I have tried to use MSS library, Memory Supervision System, version
> 1.2.1, written by Juan Jesus Alcolea Picazo and Peter Palotas, which
> allow the developer be able to detect a sort of bugs (memory leaks,
> use of uninitialized memory, out of range block accesses, "wild" or
> corrupted pointers, and more). But when I run 'make' it shows me the
> next:

[...]

> Really, I undestand what happens and what it means. It seems that
> DJGPP headers were changed since MSS was released. Maybe I have not
> the latest version of MSS. Somebody know where can I downloaded the
> workable compilable version?

The version 1.2.1 does work - see
http://libmss.sourceforge.net/manual.html#Configuring%20and%20installing%20MSS%20using%20GCC
(Whoops, what a link. Will fix that)

> Or, can I change source of MSS without
> violation of the licence?

Sure you can, that's why http://libmss.sf.net exists :)
Seriously, I've contacted original authors maybe two years ago and
they told it's OK to overtake MSS maintainership. So I did that,
version 2.0 is in the works.

Laurynas