[Scilab-users] xload mess ...

[Samuel Gougeon]

Le 16/09/2019 à 11:31, Antoine Monmayrant a écrit :
>
>
> Le 13/09/2019 à 13:38, Samuel Gougeon a écrit :
>> Hello Antoine,
> Hello Samuel,
>>
>> As discussed with you there 
>> <http://bugzilla.scilab.org/show_bug.cgi?id=15765#c4>, xload() has 
>> been restored and upgraded for Scilab 6.0.2.
>> However, its help page was updated only after the 6.0.2 release. Its 
>> update is pending
>> here <https://codereview.scilab.org/20991>, and visible in PDF there 
>> <http://bugzilla.scilab.org/attachment.cgi?id=4963>.
>>
>> As it is not possible to reproduce the issue on win7 and on Fedora, 
>> it is clear that it depends
>> on the OS, is likely specific to Ubuntu, and very likely linked to 
>> HDF5 issues reported with Ubuntu.
>>
>> However, after your recent report about the same issue on Windows 10, 
>> the confirmation
>> of the issue by any user working with 6.0.2 on Windows 10 would be 
>> welcome.
>> The test is :
>>
>>   * Download the c.scg file
>>     <http://bugzilla.scilab.org/attachment.cgi?id=4998>
>>     (http://bugzilla.scilab.org/16189)
>>   * Run : xload("c.scg")
>>
> No, that's not the test!
> Just xload("c.scg") does not crash scilab.
> As stated in the bug report ( http://bugzilla.scilab.org/16189 ) The 
> test is the following:
> // XLOAD Segfault bug
> xdel(winsid())
> xload('c.scg'); // from 5.5.2
> h=gcf()
> xsave('c2.scg',h);
> xload('c2.scg'); //bye
>
> That is you  have to xload, save a copy and xload again the copy to crash.
> I confirm this bug under another Win10 box with a colleague.
> Can you try again? 


Done. As reported on the Bugzilla thread, the instability more likely 
comes from xsave()
-- actually save() --, that changes Scilab and makes it instable.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20190917/98b278fb/attachment.htm>