Date:	Mon, 3 Jul 2000 21:23:28 +0600 (LKT)
From:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender:	kalum AT roadrunner DOT grendel DOT net
To:	djgpp AT delorie DOT com
Subject:	Re: Where can I get a Thread safe malloc debugger?
In-Reply-To:	<83og4g8c13.fsf@mercury.bitbucket>
Message-ID:	<Pine.LNX.4.21.0007032116010.1524-100000@roadrunner.grendel.net>
MIME-Version:	1.0
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

On 2 Jul 2000, The awesome and feared Nate Eldredge commented thusly,

> Unfortunately YAMD is not thread safe currently (at least I have not
> tried to make it so).

Hmm..I think you should make the effort Nate...It's pretty good stuff IMHO
but unfortunately currently I need a thread safe one..so I guess I'll have
to go after MSS..

BTW there is a good debugger called Electric Fence for Linux...I wonder
wether it's technique would work under DJGPP..heres a quote from it's
README...

"Electric Fence is a different kind of malloc() debugger. It uses the
virtual memory hardware of your system to detect when software overruns
the boundaries of a malloc() buffer. It will also detect any accesses of
memory that has been released by free(). Because it uses the VM hardware
for detection, Electric Fence stops your program on the first instruction
that causes a bounds violation. It's then trivial to use a debugger to
display the offending statement."

Would such a approach be feasible under DPMI?

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)

- Raw text -