octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: signal handling


From: John W. Eaton
Subject: Re: signal handling
Date: Thu, 14 Nov 2002 15:59:45 -0600

On 14-Nov-2002, Paul Kienzle <address@hidden> wrote:

| Can we have a debug_on_interrupt flag so that octave will stop at the
| next statement?  This can be useful if you have a long running process.
| Hit Ctrl-C, see where it has got to, then continue.  

Sure, this seems like a reasonable feature.

| One problem I see is that you don't know whether the last line ran to
| completion or if it was interrupted within an external function.  In a
| patch I sent earlier, the first interrupt would set a flag saying stop at
| the next statement, but if the user got bored waiting they could hit ctrl-C
| again which would see that the flag had been set and abort to the top
| level.

OK, so this "double interrupt" will only be required when
debug_on_interrupt is true and we are inside foreign code that would
normally jump out of the signal handler, correct?

jwe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]