[Octave-bug-tracker] [bug #51351] mktime() crashes on Windows

[Philip Nienhuis]

Follow-up Comment #6, bug #51351 (project octave):

(1) I think confirmation is needed from other people building & running
Windows dev builds. (Although it is reliably reproducible on my systems.)
Any dev cross-build from after 30 May should portray this bug.
The test build bots don't run __run_test_suite__, do they?

BTW my systems: Win7 Prof. 64bit  &  Win10 Prof. 64 bit
My build system = Mageia-5 64bit w. gcc-4.9.2


(2) (@Mike/@Rik) a test case is extremely simple (taken from time-cc.test):

t = localtime (time ())
mktime (t)

For fine builds I get 1.4-something (anyway a number) and Octave returns to a
prompt.
For the "wrong" builds Octave stalls for a few seconds and then I get the
dreaded Windows pop-up telling that Octave has just crashed ("octave-gui has
stopped working ... Problem Event Name  APPCRASH ...")

I do have an old msys setup, I use that for OF package development (mainly hg,
tar, etc). It does have gcc 4.7.2.  If I can get instructions I'm happy to try
& help out.


    _______________________________________________________

Reply to this item at:

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

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