[Octave-bug-tracker] [bug #47326] segfault in GUI and interpreter initialization

[Rik]

Follow-up Comment #4, bug #47326 (project octave):

Comment #3 from Lachlan is consistent with some sort of out-of-bounds memory
access.  I find that lots of problems disappear when I actually use gdb
because the internals of the program are re-arranged while running under the
debugger.

The fact that it only happens when QT_ACCESSIBILITY is 1 makes me think it
really is a problem with the Qt libraries, but I suppose there is a
possibility that we are doing something wrong.

I would try re-configuring and using the '--enable-address-sanitizer-flags'. 
Try 'man gcc' and search for sanitizer.

I notice in the GCC documentation that there is also a thread sanitizer
option.  You might try configuring your CFLAGS, CXXFLAGS, CPPFLAGS with that
since the segfault happens in set_default_prompts() which is the very next
function call after octave_threads::init().


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47326>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/