Date: Wed, 30 Aug 2000 08:52:11 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Bernd Becker <munin AT munin DOT inka DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: problems with YAMD (long)
In-Reply-To: <ap8oqs8joomogcm922h90qi5jmnnqtvect@4ax.com>
Message-ID: <Pine.SUN.3.91.1000830085146.7499A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Wed, 30 Aug 2000, Bernd Becker wrote:

> >What entries by YAMD did you expect?
> Well, it crashes at a point that is perfectly normal when compiled
> with GCC, so I thought it would also make an 'ERROR' entry into its
> log file or something *shrugs*.

No, the Page Fault *is* what YAMD does for you: it arranges for the
memory beyond the limits of each allocated buffer to be unmapped from
the program's address space, so that dereferencing any pointer which
points beyond the buffer immediately causes a Page Fault and pinpoints
the offending code via the traceback.  Running SYMIFY on that
traceback should show you the exact location where the bad address is
used.