1. [Phix] Fatal Exception [Memory Violation] Crashing App

I'm running Phix 1.0.0 and getting this error:

C:\CS\exchange\this_exchange.e:1627 in function init() 
fatal exception [MEMORY VIOLATION] at #0068734D 
    iniwall = {1,``} 

Please help! You're my only hope!

new topic     » topic index » view message » categorize

2. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

euphoric said...

I'm running Phix 1.0.0 and getting this error:

C:\CS\exchange\this_exchange.e:1627 in function init() 
fatal exception [MEMORY VIOLATION] at #0068734D 
    iniwall = {1,``} 

Please help! You're my only hope!

Pete! Apparently, I was also one of my hopes... because I got past it!

Here's the diagnosis:

There must be a bug somewhere when trying to assign a value to a sequence that is not yet initialized/defined.

I was trying to do something like this:

    data[NAME] = new_name 

and data[] was not yet defined/initialized.

It would be nice to just get an error message like, "You dun goofed, son," instead of a MEMORY VIOLATION ERROR! grin

I haven't used Euphoria/Phix in a while for anything serious, and I'm coming back to this particular project. But every time I use Edita, I appreciate the little conveniences and the nice functionality you've built into it. NICE JOB!

There are still some suggestions I have for it, but maybe I'll have to do that myself some day.

new topic     » goto parent     » topic index » view message » categorize

3. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

Hi

Not sure that's and undefined variable or subscript error - might be something else lurking there.

Cheers

Chris

new topic     » goto parent     » topic index » view message » categorize

4. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

ChrisB said...

Not sure that's and undefined variable or subscript error - might be something else lurking there.

Yeah, I have no idea. That's why I leave it to the professionals. grin

new topic     » goto parent     » topic index » view message » categorize

5. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

euphoric said...

It would be nice to just get an error message like, "You dun goofed, son," instead of a MEMORY VIOLATION ERROR! grin

I might have fixed something like this 2 or 3 months ago. Do both of these (uncomment one only at a time) give you decently human-readable errors?

constant NAME = 1 
sequence data 
--?data[NAME] 
 
procedure p() 
sequence data 
--?data[NAME] 
end procedure 
p() 
new topic     » goto parent     » topic index » view message » categorize

6. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

petelomax said...
euphoric said...

It would be nice to just get an error message like, "You dun goofed, son," instead of a MEMORY VIOLATION ERROR! grin

I might have fixed something like this 2 or 3 months ago. Do both of these (uncomment one only at a time) give you decently human-readable errors?

constant NAME = 1 
sequence data 
--?data[NAME] 
 
procedure p() 
sequence data 
--?data[NAME] 
end procedure 
p() 

Yes, they both give nice and clear "variable not defined" errors.

Specifically: variable data has not been assigned a value

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu