X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=tests%2Falien.impure.lisp;h=d1ee3e3adf0c3bcf1f8a32062cdbf0f5a20896b1;hb=ed891a4fd882d1b9fe066ab14bcf2107aea95baa;hp=6c6b002db65527a7ec5e0fc570a62062edb37187;hpb=09120f07344932375511dd6239ea809a6e444554;p=sbcl.git diff --git a/tests/alien.impure.lisp b/tests/alien.impure.lisp index 6c6b002..d1ee3e3 100644 --- a/tests/alien.impure.lisp +++ b/tests/alien.impure.lisp @@ -163,4 +163,44 @@ (sb-alien:deref (sb-alien:slot a1 'u) 8) (sb-alien:deref (sb-alien:slot a1 'u) 9))))) +(handler-bind ((compiler-note (lambda (c) + (error "bad note! ~A" c)))) + (funcall (compile nil '(lambda () (sb-alien:make-alien sb-alien:int))))) + +;;; Test case for unwinding an alien (Win32) exception frame +;;; +;;; The basic theory here is that failing to honor a win32 +;;; exception frame during stack unwinding breaks the chain. +;;; "And if / You don't love me now / You will never love me +;;; again / I can still hear you saying / You would never break +;;; the chain." If the chain is broken and another exception +;;; occurs (such as an error trap caused by an OBJECT-NOT-TYPE +;;; error), the system will kill our process. No mercy, no +;;; appeal. So, to check that we have done our job properly, we +;;; need some way to put an exception frame on the stack and then +;;; unwind through it, then trigger another exception. (FUNCALL +;;; 0) will suffice for the latter, and a simple test shows that +;;; CallWindowProc() establishes a frame and calls a function +;;; passed to it as an argument. +#+win32 +(progn + (load-shared-object "USER32") + (assert + (eq :ok + (handler-case + (tagbody + (alien-funcall + (extern-alien "CallWindowProcW" + (function unsigned-int + (* (function int)) unsigned-int + unsigned-int unsigned-int unsigned-int)) + (alien-sap + (sb-alien::alien-callback (function unsigned-int) + #'(lambda () (go up)))) + 0 0 0 0) + up + (funcall 0)) + (error () + :ok))))) + ;;; success