On Wed, Jan 9, 2019 at 10:54 AM Doug Stewart <address@hidden> wrote:
I tried bisecting and the problem disappeared! on both machines!I think that if you start a completely fresh build on a fresh mach. then it will fail but when you recompile the problem disappears.--DAS
I just build
HG ID for this build is "4d6392c879d7"
and again observed that the very first run terminates with signal 6 after that it runs fine:
Octave successfully built. Now choose from the following:
./run-octave - to run in place to test before installing
make check - to run the tests
make install - to install (PREFIX=/usr/local)
HG ID for this build is "4d6392c879d7"
make[2]: Leaving directory '/home/dima/src/octave/gcc_def'
make[1]: Leaving directory '/home/dima/src/octave/gcc_def'
$ ./run-octave --gui
octave exited with signal 6
$ ./run-octave --gui
./run-octave - to run in place to test before installing
make check - to run the tests
make install - to install (PREFIX=/usr/local)
HG ID for this build is "4d6392c879d7"
make[2]: Leaving directory '/home/dima/src/octave/gcc_def'
make[1]: Leaving directory '/home/dima/src/octave/gcc_def'
$ ./run-octave --gui
octave exited with signal 6
$ ./run-octave --gui
(runs fine)
In logs I see:
abrt-notification[9721]: Process 9544 (lt-octave-gui) crashed in malloc()
Dmitri.
--