URL:
<http://savannah.gnu.org/bugs/?20083>
Summary: sigaction lambda appears not to get called in 1.8.1
Project: Guile
Submitted by: gremio
Submitted on: Tuesday 06/05/2007 at 10:27
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
In my guile 1.3.4 (sorry that I do not have a more up-to-date version to play
with):
(let ((handler-called #f))
(sigaction SIGALRM (lambda (sig) (set! handler-called #t)))
(raise SIGALRM)
handler-called)
=> #t
in guile 1.8.1 it returns false. I've tried getting sigaction to display to
a port, etc., and it seems simply not to call the lambda. It's as if
sigaction set the action to SIG_IGN instead of my lambda, except that when I
query sigaction I get the appropriate (#<procedure #f (sig)> . 2), not (1 .
2). This is only slightly different from 1.3.4, where the result of the
subsequent sigaction call is (#<procedure (sig)> . 268435456) --- what is the
significance of the new #f? Is this a bug, or am I using sigaction wrong?
Thanks,
Grem
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?20083>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
