[Octave-bug-tracker] [bug #31914] datevec("03/13/1962") hangs on octave 3.3.54+ (MinGW)

[Tatsuro MATSUOKA]

Follow-up Comment #2, bug #31914 (project octave):

Hello

I have tried 
./run-octave -g

(gdb) run
 :
 :
octave.exe:1> datevec("03/13/1962")
(octave return no response)

I pressed Ctrl+C

The gdb process was terminated and I saw the shell prompt '$'.
*************
octave.exe:1> datevec("03/13/1962")
[New Thread 3068.0x27cc]

$ <- shell prompt
***********

Therefore I have abandon gdb trace and tried to insert a=1 to datevec.m as

function [y, m, d, h, mi, s] = datevec (date, varargin)
a=1 # <- here
  persistent std_formats nfmt;

And then I have tried the following from the octave prompt

*************************************************
octave.exe:1> datevec("07-Sep-2000 15:38:09")
a =  1
ans =

   2000      9      7     15     38      9
************************************************
'a=1' appear as expected.

However
*************************************************
octave.exe:2> datevec("03/13/1962")
(hanged without 'a=1')
*************************************************
????
Octave seemed to hang before function entry.

Regards

Tatsuro 


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31914>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/