1. Euphoria memory bugs
Rob,
I was having some problems with wxEuphoria, so I ran it through valgrind
under linux. I was able to pretty much instantly fix a bug that I'd been
chasing for several days.
But in doing so, I was getting some illegal reads and writes from within
exu. Some were from translated parts, and others from hand coded portions.
RHS_Slice comes to mind, as well as de_reference. It also found the
private_block bug you recently fixed (I was running an old binary).
I haven't logged this at sourceforge, because I haven't investigated too
deeply to be able to say what the problem is (it doesn't seem to cause any
problems...yet).
Matt
2. Re: Euphoria memory bugs
Matt Lewis wrote:
> Rob,
>
> I was having some problems with wxEuphoria, so I ran it through valgrind
> under linux. I was able to pretty much instantly fix a bug that I'd been
> chasing for several days.
>
> But in doing so, I was getting some illegal reads and writes from within
> exu. Some were from translated parts, and others from hand coded portions.
> RHS_Slice comes to mind, as well as de_reference. It also found the
> private_block bug you recently fixed (I was running an old binary).
>
> I haven't logged this at sourceforge, because I haven't investigated too
> deeply to be able to say what the problem is (it doesn't seem to cause any
> problems...yet).
That would be great if you could figure out
exactly where and why the illegal reads/writes are happening.
valgind sounds like a very useful tool for catching
those things.
It gives me a nice clean feeling to think
of catching and removing any subtle memory bugs. 
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Euphoria memory bugs
Robert Craig wrote:
>
> That would be great if you could figure out
> exactly where and why the illegal reads/writes are happening.
>
> It gives me a nice clean feeling to think
> of catching and removing any subtle memory bugs.
Wait, Euphoria still has bugs?!?!
