Ctrl-C crashes the application

[Giuliano Casale]

Wouldn't it be possible to disable at all the handling of ctrl-C or be
more informative on its consequences? I understand that sometimes it
works, but I regard as an unreliable aspect of Octave that I can I
lose all my data with that. At least it should be told to the user
that this combination of keys should not be used with Octave.
Giuliano

On Fri, Feb 20, 2009 at 10:58 PM, Michael Goffioul
<michael.goffioul at gmail.com> wrote:
> On Fri, Feb 20, 2009 at 8:56 PM, John W. Eaton <jwe at octave.org> wrote:
>> On 20-Feb-2009, Giuliano Casale wrote:
>>
>> | Bug report for Octave 3.0.3 configured for i686-pc-msdosmsvc
>> |
>> | Description:
>> | -----------
>> |
>> | When Octave does time consuming tasks there is sometimes the need of
>> | breaking with Ctrl-C. It is very painful that it then often crashes as
>> | well loosing previous data&work in memory.
>> |
>> | Repeat-By:
>> | ---------
>> |
>> | 1) Launch str = textread("longfile.txt","%s");
>> | 2) During execiton type CTRL-C to stop and everything crashes and closes.
>>
>> Textread is part of the Octave Forge IO package, not Octave itself, so
>> the bug could be in the textread function.
>>
>> Can you provide an example that does not rely on add-on packages?
>
> The code handling CTRL-C under Windows is complex (inherited from
> CLISP, I think) and honestly I don't understand it. It usually makes octave
> to crash. I already tried to fix that problem some months ago, but didn't
> succeed. So you'll have to live with it for the time being.
>
> Michael.
>