Re: Seg fault with test_sparse.m

[Joe Koski]

on 8/21/06 12:07 PM, John W. Eaton at address@hidden wrote:

> On 21-Aug-2006, Joe Koski wrote:
> 
> | on 8/21/06 11:10 AM, John W. Eaton at address@hidden wrote:
> | 
> | > On 21-Aug-2006, Joe Koski wrote:
> | > 
> | > | Now the only remaining error is
> | > | 
> | > | test_io.m .............................................. PASS   65/66
> FAIL
> | > | 1
> | > | 
> | > | which is unrelated to the sparse matrix package, and doesn't seem to
> affect
> | > | my day-to-day use of octave.
> | > 
> | > Can you give some more details about this failure?  What is in the log
> | > file for it?
> | > 
> | > jwe
> | 
> | John,
> | 
> | In fntests.log, the following lines report the error:
> | 
> | >>>>> processing test_io
> |   ***** test
> |  
> |  [save_status, save_files] = testls (0);
> |  [load_status, load_files] = testls (1);
> |  
> |  for f = [save_files, load_files]
> |    unlink (f{1});
> |  endfor
> |  
> |  assert(save_status && load_status);
> | !!!!! test failed
> | error: failed: mat5.mat int64
> | 
> | Apparently related to 64 bit integers? Sorry, I don't know the status of Mac
> | support for 64 bit integers in OS X 10.4.7. I do know that they don't claim
> | full 64 bit support yet.
> 
> Does OS X have 64-bit long long integers?  Search for
> HAVE_LONG_LONG_INT=1 and SIZEOF_LONG_LONG=8 in the output from
> octave_config_info.
> 
> jwe

John,

I searched octave_config_info. For HAVE_LONG_LONG_INT, there are two
instances of -DHAVE_LONG_LONG_INT=1 in UGLY_DEFS and DEFS. For
SIZEOF_LONG_LONG there are again two instances of -DSIZEOF_LONG_LONG=8 in
the same two variables (UGLY_DEFS and DEFS). Otherwise, the strings don't
occur.

In my config.log for octave-2.9.7, I have

#define HAVE_LONG_LONG_INT 1

several times, and 

#define SIZEOF_LONG_LONG 8

also several times.

So apparently, octave thinks that it has 64 bit integer support.

Joe