octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54920] sigabrt (signal-6) crash with AutoScal


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #54920] sigabrt (signal-6) crash with AutoScale in xscale = log mode
Date: Thu, 1 Nov 2018 14:57:17 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #13, bug #54920 (project octave):

Panxto: I started thinking about your suggestion a bit more and I'm wondering
just how it would work.  Suppose some code running in the GUI thread calls a
function that results in a call to Octave's error function.  With your
suggested change, the error function would determine that it was not running
in the interpreter thread call octave_link function that would ultimately call
error again, but in the interpreter thread.  That part I can understand
working, but then what happens in the GUI thread?  Presumably we are in a
situation where we should not continue because there was an error, but how do
we detect that?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54920>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]