[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #43043] Segfault with CTRL-C
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #43043] Segfault with CTRL-C |
Date: |
Wed, 27 Aug 2014 05:35:41 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 |
Update of bug #43043 (project octave):
Category: None => Libraries
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #6:
So I'm not sure if Octave can do much on this bug, marking as won't fix. I'm
not sure what's going on or what you're comparing, to be honest, but it looks
like the problem is that OpenBLAS cannot be interrupted while performing some
operation across multiple threads. I am unable to reproduce this myself, using
OpenBLAS 0.2.10 on Debian testing, 30 or so times Ctrl-C and no segfault.
Octave's part in this is to detect the user interrupt and break out of the
stack of whatever BLAS library routine is executing at the time. This works
for standard BLAS, and I suppose is expected to work with any BLAS drop-in
replacement.
See the following, might be the same problem and may be something that gets
fixed in OpenBLAS:
* https://github.com/xianyi/OpenBLAS/issues/378
* https://github.com/JuliaLang/julia/issues/1468
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43043>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/