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

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

[Octave-bug-tracker] [bug #51886] Ctrl-C crash is back


From: Lars Kindermann
Subject: [Octave-bug-tracker] [bug #51886] Ctrl-C crash is back
Date: Tue, 29 Aug 2017 17:57:10 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

Playing with gdb revealed some strange behaviour, maybe you can make sense of
it:

After attaching gdb to the gui process, setting
(gdb) handle SIGINT pass nostop
(gdb) finish
and pressing a few times enter until all threads are back to normal, the gui
can be used again.

After pressing Ctrl-C once in the octave command window gdb shows that the
threads lt-octave-gui and QThread receive SIGINTs repeatedly forever - until I
enter some command in the gui,
e.g. a=1. Then the SIGINT storm stops until the next Ctrl-C.
No crash happens when gdb is attached this way.

Shouldn't send Ctrl-C not only a *single* SIGINT to each thread?
Maybe this continuous series of signals will eventually crash one of the
threads if it cannot handle them in time. 

This could explain the variyng and intermittend behaviour on different systems
and why it is not happening under gdb: gdb catches SIGINT first before it
sends it to the program with a slower pace...  



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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