[Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults

[Mike Miller]

Follow-up Comment #70, bug #37672 (project octave):

That's pretty interesting.

Here's what the thread state looks like with ./run-octave -qfH --no-gui


(gdb) info threads
  Id   Target Id         Frame 
  9    Thread 0x7f90b6d75700 (LWP 20771) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  8    Thread 0x7f90b6574700 (LWP 20772) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  7    Thread 0x7f90b5d73700 (LWP 20773) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  6    Thread 0x7f90b1572700 (LWP 20774) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  5    Thread 0x7f90aed71700 (LWP 20775) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  4    Thread 0x7f90ac570700 (LWP 20776) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  3    Thread 0x7f90a9d6f700 (LWP 20777) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  2    Thread 0x7f909adb6700 (LWP 20778) "QThread" 0x00007f90cc0a4b83 in
select ()
    at ../sysdeps/unix/syscall-template.S:84
* 1    Thread 0x7f90cfd39940 (LWP 20638) "lt-octave-gui" 0x00007f90cc0a2dcd in
poll ()
    at ../sysdeps/unix/syscall-template.S:84


And here's what gdb sees with OMP_NUM_THREADS=1 ./run-octave -qfH --no-gui


(gdb) info threads
  Id   Target Id         Frame 
  2    Thread 0x7f8f005e9700 (LWP 20992) "QThread" 0x00007f8f200d0b83 in
select ()
    at ../sysdeps/unix/syscall-template.S:84
* 1    Thread 0x7f8f23d65940 (LWP 20852) "lt-octave-gui" 0x00007f8f200cedcd in
poll ()
    at ../sysdeps/unix/syscall-template.S:84


These additional threads are running on behalf of OpenBLAS for me, so
something at startup triggers a BLAS routine to be called and kick off the
OpenBLAS worker threads.

    _______________________________________________________

Reply to this item at:

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

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