[Scilab-Dev] EXCEPTION_ACCESS_VIOLATION

[Сергей]

Dear Francois,
I didn't draw my attention to you comments with the "basic_sex.sci" :)))
Actually "basicsex.sci" name means "basics examples". I have never thought somebody can misapprehend this as basic sex! :)))

ad rem...
I've installed Scilab 4.2.1 and still can see this critical issue. It looks like some internal problems in Scilab with the stack, since I believe users (people who coding in sci files) MUST not be able to raise such kind of exceptions. As I said all further actions with SciLab after that are not allowed.  

Does anybody in this list who can work on this problem? Problem is seen if I execute the script from scipad (execute->load into silab), but if I type exec('basicsex.sci') in Scilab main window the issue is not seen. I can send more detailed instruction if somebody in this list is ready to work on it. 


Regards,
Sergey
-----Original Message-----
From: François Vogel [mailto:fvogelnew1 at free.fr] 
Sent: Friday, May 02, 2008 3:36 PM
To: Сергей
Cc: Scilab dev list
Subject: Re: [Scilab-Dev] EXCEPTION_ACCESS_VIOLATION

You have to understand that from the point of view of security, 
executing your stuff having hundreds of lines in it and not having a 
clue about what it is supposed to do (format hard disk?), is a really 
stupid thing to do, especially when the main script is named 
basic_sex.sci.

Anyway.

OK, since you're sympathetic, let's have a look in virtual machines I 
will delete right after having created them specially for you.

- Mandriva 2008.1 with Scilab 4.2.1: can't reproduce
- Windows with Scilab 4.2.1: can't reproduce neither.

Not in the mood for trying with Scilab 4.1.1, which is quite old.

Francois


Сергей said on 02/05/2008 21:31:
> No problem,
> If you don't want to investigate the possible problem with your product it's your business not mine... I just tried to help since this issue looked critical. So you are welcome
> 
> -----Original Message-----
> From: François Vogel [mailto:fvogelnew1 at free.fr] 
> Sent: Friday, May 02, 2008 9:44 AM
> To: Сергей
> Cc: dev at lists.scilab.org
> Subject: Re: [Scilab-Dev] EXCEPTION_ACCESS_VIOLATION
> 
> Hi,
> 
> Personally I will not try to find what is your problem: your case 
> looks very much fishy. You send a large number of files and ask us to 
> execute them. Who knows what those files are doing? Try do trim down 
> your problem before submitting.
> 
> And a script named basicsex.sci looks very suspicious to me too...
> 
> Should you really not be a spammer, the only advice I could give you 
> is to upgrade to Scilab 4.1.2 or 4.2 instead of sticking with 4.1.1. 
> If the problem still happens, trim it down to a few lines before 
> submitting.
> 
> Sorry, guy...
> 
> Francois
> 
> 
> Сергей said on 01/05/2008 10:41:
>> Hello SciLab team.
>>
>>  
>>
>> Can you please help me with the bug I have with SciLab( I use scilab 4.1.1)
>>
>>  
>>
>> How to reproduce:
>>
>>  
>>
>>    1. Extract attached zip file to some folder.
>>    2. in scilab change current directory to the folder ../scilab_yalmip
>>    3. execute the file ../scilab_yalmip/init.sci
>>
>>  
>>
>> Now  open the file *../scilab_yalmip/demos/basicsex.sci* and execute 
>> this script. 
>>
>> After the script execution has finished try to click the button “open 
>> file” in scilab environment you will get an error message:
>>
>>  
>>
>> Scilab has found a critical error (EXCEPTION_ACCESS_VIOLATION)
>>
>> Scilab may become unstable
>>
>>  
>>
>>  
>>
>> After that further working with SciLab is impossible.
>>
>>  
>>
>>  
>>
>> BR,
>>
>> Serega
>>
> 
> 
>