seg-fault of octave on MacOSX

[John W. Eaton]

On  6-Dec-2007, Jean-François Mertens wrote:

| 
| On 06 Dec 2007, at 19:17, John W. Eaton wrote:
| 
| > Since the crash is happening inside of Fsave, I think it must be one
| > of the lines
| >
| >     save ("-binary", nm, "f2", "g2", "h2");
| >
| > What happens if you just execute
| >
| >   a = 2;
| >   f = @(x) a + x;
| >   g = @(x) 2 * x;
| >   h = @log2;
| >   f2 = f;
| >   g2 = g;
| >   h2 = h;
| >   nm = tmpnam();
| >   save ("-binary", nm, "f2", "g2", "h2");
| 
| Right _ fails too _ and already much smaller !
| output:
| ....
| octave:8> nm = tmpnam();
| octave:9> save ("-binary", nm, "f2", "g2", "h2");
| 
| Program received signal EXC_BAD_ACCESS, Could not access memory.
| Reason: KERN_INVALID_ADDRESS at address: 0x756f6d79
| 0x756f6d79 in ?? ()
| (gdb) bt
| #0  0x756f6d79 in ?? ()
| #1  0x1176fd10 in std::basic_filebuf<char, std::char_traits<char>  
|  >::_M_terminate_output (this=0x12e0a650) at /sw/.bld/ 
| gcc42-4.2.2-1000/darwin_objdir/i686-apple-darwin8/libstdc++-v3/ 
| include/bits/fstream.tcc:765
| #2  0x010e1f59 in save_vars (os=@0xbfff81a8, pattern=@0x12ec18a8,  

Did you see this message:

  https://www.cae.wisc.edu/pipermail/bug-octave/2007-December/004243.html

?  Are you building with -fPIC?

jwe