Mail Archives: djgpp/2000/07/03/16:16:36
Kalum Somaratna aka Grendel <kalum AT lintux DOT cx> writes:
> 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..
Yes, thread-safety is on the TODO list. The main problem is that I
haven't any experience with threads, so I need to educate myself.
After that I think it won't be much more than adding locks in a few
places.
>
> 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."
This is just what YAMD does, but YAMD also does more bookkeeping, and
has some other useful features as well (IMHO of course :)
--
Nate Eldredge
neldredge AT hmc DOT edu
- Raw text -