X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Date:	Sat, 11 Dec 2004 12:58:01 +0200
From:	"Eli Zaretskii" <eliz AT gnu DOT org>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-ID:	<01c4df70$Blat.v2.2.2$6ddabf00@zahav.net.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 2.2.2
In-reply-to:	<41BA307B.B402D23C@yahoo.com> (message from CBFalconer on Fri, 10
	Dec 2004 18:25:47 -0500)
Subject:	Re: Bison 1.875 (release 2)
References:	<5CDCE8E138ACB445B11E9F7B85FC782A1AAB8A AT radon DOT smr DOT intern> <01c4deae$Blat.v2.2.2$99d27980 AT zahav DOT net DOT il> <41B9977F DOT AE71420B AT yahoo DOT com> <01c4df08$Blat.v2.2.2$4ed91b00 AT zahav DOT net DOT il> <41BA307B DOT B402D23C AT yahoo DOT com>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Fri, 10 Dec 2004 18:25:47 -0500
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> 
> I can see how that is much more immediate at catching overwrites,
> etc.  You are aware that nmalloc includes a SAVEMEMORY define that
> removes guard words at the ends of allocations, which in turn
> enables most overwrites to be detected early (at the cost of some
> overhead).

The problem with detecting such bugs is that, unless you run the
detection code after every machine instruction, you cannot detect them
except at some later moment, and that makes it hard to find the buggy
code without further debugging.

YAMD in effect puts a hardware-assisted watchpoint near the edges of
every allocated buffer, so code that accesses invalid memory is caught
right on the spot.

That said, since YAMD has its limitations (e.g., large programs such
as Emacs and GDB cannot at all be run under YAMD), I think any
debugging tools such as malldbg and nmalloc are welcome additions to
our toolchest.

- Raw text -