From: Alastair B. <nye...@li...> - 2006-11-28 23:25:25
Attachments:
win32-exception-unwind.diff
|
Hello all, Attached is a patch (tested on XPSP2) to correctly unwind foreign exception frames when doing a non-local exit through alien code (such as would happen if you did an abort to toplevel in the debugger from a window procedure). This was item 4b on my old TODO.Win32, which tells you how long we've known about it. The fact that nobody else ran into it probably tells you something else. --Alastair Bridgewater |
From: Nikodemus S. <nik...@ra...> - 2006-11-30 17:10:43
|
Alastair Bridgewater <nye...@li...> writes: > Hello all, > > Attached is a patch (tested on XPSP2) to correctly unwind foreign > exception frames when doing a non-local exit through alien code (such > as would happen if you did an abort to toplevel in the debugger from a > window procedure). Do you happen to have a test-case handy? Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |
From: Alastair B. <nye...@li...> - 2006-12-01 03:26:35
Attachments:
exception-unwind-test.lisp
|
Nikodemus Siivola writes: > Alastair Bridgewater <nye...@li...> writes: > >> Hello all, >> >> Attached is a patch (tested on XPSP2) to correctly unwind foreign >> exception frames when doing a non-local exit through alien code (such >> as would happen if you did an abort to toplevel in the debugger from a >> window procedure). > > Do you happen to have a test-case handy? My test case was somewhat less than succinct (involving two tarballs, a minor code change, and some interaction), so I put together a minimal one for you. Attached. --Alastair Bridgewater |