[bf1942] Another stacktrace

[Scratch Monkey]

--On Friday, December 13, 2002 8:37 PM -0500 "Ryan C. Gordon"
<icculus at clutteredmind.org> wrote:

> As you might have guessed, this is almost certainly a memory corruption
> bug.

Ouch! Those can be nasty to find. Can you set up some way to watchpoint the
bad location so the program will stop on failure? This might require an
iterative process since it only happens in the field: Catch the exception
and record the bad data and address, then run again with the watchpoint set
to see when that location gets that data written.