[armedbear-ticket] [armedbear] #304: Stack abstraction inconsistency between Java and Lisp frames

[armedbear]

#304: Stack abstraction inconsistency between Java and Lisp frames
-------------------------+--------------------------------------------------
 Reporter:  mevenson     |       Owner:  ehuelsmann
     Type:  defect       |      Status:  new       
 Priority:  major        |   Milestone:  1.2.0     
Component:  interpreter  |     Version:  1.2.0-dev 
 Keywords:  needs-test   |  
-------------------------+--------------------------------------------------
 The stack abstraction maintained by LispThread.java can get very large,
 seemingly containing a frames that should long ago have been popped.

 I believe this is happening when we push "Java stack frames" via
 Lisp.pushJavaStackFrame() when some part of the implementation calls
 Lisp.error().  These frames are never cleaned up properly by an
 appropriate pop.

 Instead of pushing this information to the LispThread stack, the
 information could possibly be added to the appropriate Lisp frame to be
 output in a backtrace.

-- 
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/304>
armedbear <http://common-lisp.net/project/armedbear>
armedbear