Re: JIT compiler changeset results in plot failure with segfault

[Michael Goffioul]

On Sat, Nov 2, 2013 at 3:41 AM, John W. Eaton <address@hidden> wrote:

I noticed that "sombrero" was failing for me by causing Octave to exit
with a segfault.  Bisecting shows this changeset as the first bad one:

  The first bad revision is:
  changeset:   17792:26e9312e6928
  user:        Rik <address@hidden>
  date:        Tue Oct 29 11:09:49 2013 -0700
  summary:     Build JIT compiler by default, but do not enable it by default.

I don't understand how this could cause trouble for plotting,
especially if it the jit compiler is disabled by default.

Is anyone else able to reproduce this problem, or is it just me?

If I install and run octave-gui directly under gdb, I get the
following traceback.  Note that it appears to be crashing in LLVM.
If LLVM is disabled, that really shouldn't be happening, should it?

I guess not, except if you have a memory corruption somewhere that messes up with the gdb stack. Maybe running it into valgrind can reveal something. I also noticed 2 different versions of LLVM in the backtrace: frame #2 uses libLLVM-3.2.so.1, while frames #0 and #1 use libLLVM-3.0.so.1. Maybe this is normal, but I figured I mentioned it.

Michael.