[ clisp-Bugs-1220548 ] unwind-protect confuses abort restart

[SourceForge.net <no...@so...>]

Bugs item #1220548, was opened at 2005-06-14 18:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1220548&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jörg Höhle (hoehle)
Assigned to: Nobody/Anonymous (nobody)
Summary: unwind-protect confuses abort restart

Initial Comment:
Hi,

I mentioned that in clisp-devel around October 2004
["confused debugger, aborts to outer break level --
repeatable"], but did not submit a bug report. The bug
is still in clisp-cvs.

When there's an unwind-protect frame somewhere on the
stack, restarts may get confused. As a result, Lisp
sessions get mixed up (e.g. today it affected my SLIME
session).
I originally noticed this with cl-sql, which uses
with-foreign-string, which does the same as unwind-protect.

[17]> (unwind-protect (error "hi") (print "out"))
*** - hi
Mögliche Optionen:
ABORT          :R1      ABORT
Break 1 [18]> (unwind-protect (error "hi") (print "out"))
*** - hi
Mögliche Optionen:
ABORT          :R1      ABORT
ABORT          :R2      ABORT
Break 2 [19]> abort
"out" 
"out" 
[20]>
Failed Expectation: get out only one level. The :r1
restart does this correctly.

In contrast, using the :r1 restarts gets out only one
level, as expected.
This also happens using the interpreted memory image.

Regards,
 Jörg Höhle

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1220548&group_id=1355