[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes seg
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults |
Date: |
Sat, 11 Jun 2016 20:33:00 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #71, bug #37672 (project octave):
I get something similar with gdb which shows that the call to
system ("", 1)
really just succeeds in closing down the extra OpenBlas threads which is why
subsequent Ctrl+C keystrokes work.
The debug session is below.
>> pause (2)
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7fffdf51f700 (LWP 19368)]
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or
directory.
(gdb) info threads
Id Target Id Frame
5 Thread 0x7fffd49f8700 (LWP 19371) "QThread" 0x00007ffff440253d in
nanosleep () at ../sysdeps/unix/syscall-template.S:81
4 Thread 0x7fffda51d700 (LWP 19370) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
3 Thread 0x7fffded1e700 (LWP 19369) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 2 Thread 0x7fffdf51f700 (LWP 19368) "lt-octave-gui"
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
1 Thread 0x7ffff7f91840 (LWP 19293) "lt-octave-gui" 0x00007ffff4123b1d in
poll () at ../sysdeps/unix/syscall-template.S:81
(gdb) list
180 in ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
(gdb) c
Continuing.
>>
>> system ("", 1)
ans = 0
>> pause (2)
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7fffd49f8700 (LWP 19371)]
0x00007ffff440253d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
81 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) info threads
Id Target Id Frame
* 5 Thread 0x7fffd49f8700 (LWP 19371) "QThread" 0x00007ffff440253d in
nanosleep () at ../sysdeps/unix/syscall-template.S:81
1 Thread 0x7ffff7f91840 (LWP 19293) "lt-octave-gui" 0x00007ffff4123b1d in
poll () at ../sysdeps/unix/syscall-template.S:81
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?37672>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, (continued)
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Rik, 2016/06/08
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/08
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/08
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/08
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Rik, 2016/06/09
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/09
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Rik, 2016/06/10
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/10
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Rik, 2016/06/10
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Mike Miller, 2016/06/10
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults,
Rik <=
- [Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults, Lachlan Andrew, 2016/06/27