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

[Rik]

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

See bug #47372 where I was able to get the address sanitizer running with gcc.
 There are certainly memory leaks.

After great effort, I was able to get the thread sanitizer running.  I've
attached the log as thread.log to this report.  Sure enough there is a
reported data race condition between threads in set_default_prompts().  My
guess is that is what is causing the segfault for you.

I'm no help in fixing this though as I never mess around with the GUI.

(file #36588)
    _______________________________________________________

Additional Item Attachment:

File name: thread.log                     Size:9 KB


    _______________________________________________________

Reply to this item at:

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

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