Re: Segmentation Fault with Octave MXE under Windows

[PhilipNienhuis]

ijourneaux wrote
> Just moving this over to the Octave-Maintainers list.
> 
> Still trying to figure out what is causing this segmentation fault.
> 
> Here is the bug post
> 
> https://savannah.gnu.org/bugs/?41699
> 
> The easiest way to replicate the error is
> 
> test imread
> exit(0)
> 
> This results in the segfault. If I run octave with gdb you get the
> following additional info.
> 
> warning: Invalid parameter passed to C runtime function. 
> error: writing file 'U:\.octave_hist': No such file or directory 
> error: ignoring octave_execution_exception while preparing to exit 
> Program received signal SIGSEGV, Segmentation fault. 
> 0x68a807c0 in liboctinterp-2!_ZN5ArrayIdED2Ev () 
> from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll

Have you checked if U:\.octave_hist  exists and is writable?

I remember similar behavior from older Octave versions (> 3-4 years ago)
that put the history file in a read-only location; IIRC JWE fixed something
related ~ 2 years back.

You could try to change the history file to some other location (put that
command in .octaverc), that helped me.

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Segmentation-Fault-with-Octave-MXE-under-Windows-tp4664305p4664314.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.