octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: exec segfaults on Windows.


From: Tatsuro MATSUOKA
Subject: Re: exec segfaults on Windows.
Date: Wed, 4 May 2016 08:08:23 +0900 (JST)

>From: Rik <address@hidden>
>To: Tatsuro MATSUOKA <address@hidden> 
>Cc: address@hidden
>Date: 2016/5/4, Wed 02:00
>Subject: Re: exec segfaults on Windows.
> 
>
>On 05/02/2016 10:44 PM, address@hidden wrote:
>
>Subject:  exec : typo in documents and erroneously terminates on native 
>windows 
>>From:  Tatsuro MATSUOKA <address@hidden> 
>>Date:  05/02/2016 10:30 PM 
>>To:  "address@hidden" <address@hidden> 
>>List-Post:  <mailto:address@hidden> 
>>Precedence:  list 
>>MIME-Version:  1.0 
>>Reply-To:  Tatsuro MATSUOKA <address@hidden> 
>>Message-ID:  <address@hidden> 
>>Content-Type:  multipart/mixed; 
>>boundary="551173151-880950786-1462253419=:63132" 
>>Message:  4 
>>
>>Hello I have execute exec on native windows (4.0.2) and Cygwin (4.0.1) In the 
>>documents(help and manual) *******************************
     FILE.  For example,           exec ("ls" "-l")      will run 'ls' and 
return you to your shell prompt.
*******************************
          exec ("ls" "-l")
should be
          exec ("ls", "-l")
(missing comma) BTW, octave termination of octave by exec ("ls", "-l") is an 
expected behavior.
However, octave erroneously terminates on octave 4.0.2 (32 and 64 bit)
I attached message from Windows. (Sorry it is written in Japanese.)

Translation
 Octave-cli is terminated.
 Problems occurred and program does not work correctly.
 Program is terminated by windows system.
 If there is a solution, it is reported from windows system.
    (Button [Terminate program]) Tatsuro 
5/3/16
>
>Tatsuro,
>
>The documentation string is incorrect as you noted.  I fixed that
    here http://hg.savannah.gnu.org/hgweb/octave/rev/32a6d948fea7.


Thanks!


>I just tried exec with 4.0.2-cli in a Windows XP virtual machine and
    there is an indication of going through an emergency shutdown which
    is incorrect, although the eventual shell command is executed
    correctly.  See below
>
>>> exec ('dir')
>panic: Segmentation violation -- stopping myself...
>attempting to save variables to 'octave-workspace'...
>abc                IETldCache         ntuser.dat.LOG        SendTo
>Application\ Data  Local\ Settings    ntuser.ini            Start\
    Menu
>Cookies            MapSetToolKit.cfg  PrintHood            
    Templates
>Desktop            My\ Documents      PrivacIE              UserData
>Favorites          NetHood            QBInstanceFinder.log  WINDOWS
>g2mdlhlpx.exe      NTUSER.DAT         Recent
>
>Could you file a bug report about that on the bug tracker?
>


Done.


http://savannah.gnu.org/bugs/?47840


Tatsuro



reply via email to

[Prev in Thread] Current Thread [Next in Thread]