Open michaelkarlcoleman opened 6 years ago
@tutufan I'm indeed seeing the same problem using Octave/4.2.1-intel-2017a
, I've only used the CLI version of Octave up until now...
This may be related to a very similar issue I have been seeing with Spyder
(using intel/2017b
) , see https://github.com/spyder-ide/spyder/issues/4624 .
I was planning to push this through valgrind
with a Qt5
build that includes debug symbols, but didn't get to that yet (and I probably won't anytime soon...).
At least on recent develop branch, both the -mt and plain versions of Octave-4.2.1-intel-2017a segfault immediately when run with X11. (They start fine without DISPLAY). This was compiled on a vanilla centos-7 image, and run on a RedHat 7.4 host.
Anyone else seeing this?