On Dec 3, 2007, at 10:20 PM, Ben Abbott wrote:
On Dec 3, 2007, at 12:07 PM, John W. Eaton wrote:
I've located a specific failure, but am not sure it is a bug, or a
feature of the way I've build octave.
"test datevec" produces a kernel panic. After some testing I found
that any date string with either ":" or "/" give that result. Thus,
each of the following ...
datevec("07-Sep-2000 15:38:09")
datevec("07-Sep-2000")
datevec("09/07/00")
datevec("09/13")
datevec("15:38:09")
datevec("3:38:09 PM")
datevec("15:38")
datevec("03:38 PM")
datevec("03/13/1962")
... produce
---------------------------------
panic: Bus error -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Bus error
---------------------------------
While the following work as expected
datevec("07-Sep-2000 15:38:09")
datevec("07-Sep-2000")
all(datenum(datevec([-1e4:1e4]))==[-1e4:1e4]'))
t = linspace (-2e5, 2e5, 10993);
all (abs (datenum (datevec (t)) - t') < 1e-5));
I've built octave on an intel Mac using Fink's package management. The
config parameters and build script are below
---------------------------------
ConfigureParams: F77=%p/bin/g95 --libexecdir='${prefix}/lib'
CompileScript: <<
#!/bin/sh -ev
gcclib=`%p/bin/g95 --print-lib`
FLIBDIR=`dirname $gcclib`
export FLIBS="-L${FLIBDIR} -lf95"
export FFLAGS='-O2'
export CFLAGS='-O2'
export CXXFLAGS='-O2'
./configure %c
make
make check
---------------------------------
I'm hoping someone will point out that I've made an error. If not I'll
file a bug report.
Ben
oppps, the failures should have been
datevec("09/07/00")
datevec("09/13")
datevec("15:38:09")
datevec("3:38:09 PM")
datevec("15:38")
datevec("03:38 PM")
datevec("03/13/1962")
Ben