Wrong closure values in the debugger

Bug #1099500 reported by Stas Boukarev on 2013-01-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

(let ((a 1))
    ((f1 ()
       (princ a)
       (incf a)
     (f2 ()

  0: ((LABELS F1))
        A = 70368591571592
  1: ((LABELS F2))
        A = 70368591571592
  2: ((LAMBDA ()))
        A = 2

Reported by flip214 on #sbcl

I haven't tried to replicate this, but it seems likely to me that the
closure value cell in question has been d-x allocated, and thus is stored
on the stack... And I don't recall ever looking into debugger interactions
with the d-x value cell changes.

Anyway, a possible starting point if someone wants to dig into this.

Stas Boukarev (stassats) wrote :

In 000a07de2a12437af30f28e75b39037b2bb6d63f

Changed in sbcl:
status: Triaged → Fix Committed
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers