[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47927] Ctrl+C crashes Octave on MacOS
|
From: |
Lachlan Andrew |
|
Subject: |
[Octave-bug-tracker] [bug #47927] Ctrl+C crashes Octave on MacOS |
|
Date: |
Mon, 16 May 2016 09:59:03 +0000 (UTC) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Update of bug #47927 (project octave):
Summary: Ctrl+C crashes Octave => Ctrl+C crashes Octave on
MacOS
_______________________________________________________
Follow-up Comment #2:
I can't reproduce this on Linux, so I've added "on MacOS" to the summary.
The log says that it is accessing a NULL pointer within the readline library
itself, in rl_read_key.
Thread 5 seems to be at the same point as Thread 0, the one that crashed,
until the innermost stack frame. Thread 5 is performing a __select, whereas
Thread 0 is in rl_read_key.
It seem odd. Would you be able to do a code bisection to find where it
started?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47927>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/