OpenEuphoria

RE: EXW Crashes!

• Posted by Andy Drummond <kestrelandy at xalt.co.uk> Apr 27, 2001
• 446 views

Thanks for the suggestion. Unfortunately when I use safe.e in place of 
machine.e it crashes immediately. Comes up saying 'Using debug ....' 
etc, press Enter & instantly Bang! fails at 7675916 (#0075200C). For any 
and all .EXW programs. So either I have a buggy EXW or a buggy Safe.e or 
a buggy PC or a buggy brain.

I will look, in the meantime, for any possible poke of illegal data or 
calls to poked code after the memory has been released etc etc.

Any further comments (polite ones, even) welcome. I will re-install 
Euphoria from the disk - I'm glad I got a disk and not just a 
download...

Andy

Chris Bensler wrote:
> I don't know why your not getting Ex.err for subscript out of bounds..
> You should, I do...
> 
> The secoond error isn't a Euphoria error at all.. It means that you 
> tried to make an invalid memory assignment. It's a problem in your 
> code.. (usually your trying to poke data to unallocated memory..)
> 
> A lot of times when you get those errors, you can run your program using 
> 
> safe.e instead of machine.e, and it will tell you what the problem is..
> 
> To use safe.e, just rename safe.e to machine.e. Make sure you rename the 
> 
> original machine.e first though..
> 
> I don't know how well safe.e will work with win32lib though... don't 
> have experience with it..
> 
> Chris
> 
> 
> Andy Drummond wrote:
> > I have two problems with EXW which maybe someone can shed some light on.
> > 
> > The first is that when I get an error with sequence subscripts out of 
> > range - like reading 20th element of a sequence of length 19 - I don't 
> > get a ex.err file generated. This is particularly annoying as the 
> > DOS-style dump is just not enough lines to show the place where the 
> > error occurred. Any ideas?
> > 
> > The second is worse. The advertising for Euphoria tells me it won't 
> > crash and when it finds a fault it will produce a meaningful message. 
> > Not so. I keep getting errors with EXW trying to access 0xffffffff, 
> > which the OS doesn't care for.  The "details" from the Win98 crash 
> > message is as follows. Should it go to RDS do you think?
> > 
> > 
> > EXW caused an invalid page fault in
> > module <unknown> at 0000:007f83e0.
> > Registers:
> > EAX=00000001 CS=0167 EIP=007f83e0 EFLGS=00010216
> > EBX=007f83e0 SS=016f ESP=0056f940 EBP=0056f94e
> > ECX=008569c4 DS=016f ESI=007f83e0 FS=3faf
> > EDX=007f8290 ES=016f EDI=00000008 GS=0000
> > Bytes at CS:EIP:
> > 20 00 7e 00 fc 84 7f 00 ba f3 83 7f 00 88 02 5a 
> > Stack dump:
> > 0041454c 0056f998 bff7363b 00000544 00000020 00000544 02000001 89961317 
> > 00000000 00000000 00000000 00000000 00000000 007f83e0 007f846b 005689b6 
> > 
<snip>