Re: New Bug [Attn: Robert Craig]
Robert Craig wrote:
> If you use peeks and pokes it is almost certainly
> your own bug. The fact that the location of the crash varies
> after trivial changes to the code does not impress me much.
> That's par for the course with this sort of memory corruption error.
> You might be writing some data just one byte beyond the space
> you allocated, thereby corrupting some Euphoria variable, and
> causing an eventual crash far from where you did the poke.
>
> The first thing you should do is read the instructions at
> the top of safe.e in euphoria\include. By copying safe.e
> into your current directory and using it in place of machine.e
> you might catch your bug very easily.
Actually, I just changed include machine.e into include safe.e, and again, it
was a red harring. After running with safe.e, I found that I was poking a
0 byte into memory, that wasn't allocated for my usage. With that, it was
destroying Euphoria's internal Memory Space. So with that in mind, I again
cried wolf. So, from now on, I will extensivly test stuff, and see if I
can't find a way around the bug, or if there's an error in my syntax, before
reporting anything.
Mario Steele
|
Not Categorized, Please Help
|
|
