Opened 13 years ago

Closed 12 years ago

#102 closed defect (fixed)

SLIME bugs on x8664

Reported by: alms Owned by: GB
Priority: major Milestone:
Component: Slime Version: 1.1
Keywords: Cc:

Description (last modified by gb)

I'm entering these SLIME / debugging problems as a Trac Ticket in light of a customer's recent e-mail about their Lisp requirements ("It would be awfully nice if the debugging information generated by the compiler allowed for easier debugging, e.g., better display of args and locals, return from frame, restart frame. Integration with Slime is a must.")

SLIME has not been updated to account for recent changes made in OpenMCL to support x86-64 processors. You may run into bugs running on those platforms.

The SLIME backtrace sometimes shows incorrect information.

return-from-frame and apply-in-frame do not work reliably. (If they work at all, it's pure luck.)

Change History (4)

comment:1 Changed 13 years ago by gb

  • Description modified (diff)

comment:2 Changed 13 years ago by rme

I sent mail to slime-devel suggesting that swank-openmcl.lisp use CCL::CLOSURE-CLOSED-OVER-VALUES, or at least use CCL::NTH-IMMEDIATE instead of CCL::%SVREF when displaying closed-over values.

(See also ticket:109)

comment:3 Changed 13 years ago by rme

The closure-closed-over-values patch is now in the SLIME tree. (The code uses NTH-IMMEDIATE now.)

comment:4 Changed 12 years ago by rme

  • Component changed from Compiler to SLIME
  • Resolution set to fixed
  • Status changed from new to closed

I think that SLIME is working reasonably well now; if there are further issues, let's open up new individual tickets for them, and set the ticket's "component" field to SLIME.

Note: See TracTickets for help on using tickets.