Catching user interrupts

Catching user interrupts

[Andy Wingo]

Hi gang,

I'm running into trouble catching interrupts. It always works the first
time, but the second time I run a piece of code in the repl it becomes
unresponsive. For example:

(catch #t
       (lambda () (while #t #t))
       (lambda (key . args)
	 (if (not (eq? key 'signal))
	     (apply throw key args))))

Try that twice in your repl.

I've tried a lot more methods (sigaction throwing 'interrupt, sigaction
setting a system async to throw 'interrupt), but nothing works the
second time. Any clues? Thanks.
-- 
Andy Wingo <wingo@pobox.com>


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user

Re: Catching user interrupts

[Marius Vollmer]

Andy Wingo <wingo@pobox.com> writes:

> I'm running into trouble catching interrupts. It always works the first
> time, but the second time I run a piece of code in the repl it becomes
> unresponsive. For example:
>
> (catch #t
>        (lambda () (while #t #t))
>        (lambda (key . args)
> 	 (if (not (eq? key 'signal))
> 	     (apply throw key args))))
>
> Try that twice in your repl.

Strange.  Try this variant

  (catch #t
         (lambda () (while #t #t))
         (lambda (key . args)
           (unmask-signals)                 ;;; <- this is new
 	   (if (not (eq? key 'signal))
 	     (apply throw key args))))

Somehow, signals end up being 'masked' after your code loop is
interrupted.  I haven't yet investigated why, tho.

This problem does not occur in 1.7, which has a quite different way to
handle signals internally.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user