Steel Bank Common Lisp

suboptimal error message when attempting to trace an undefined function

Reported by Cyrus Harmon on 2011-03-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Low
Unassigned

Bug Description

When attempting to trace an undefined function like so:

SPECTACLE> (trace moose)

SBCL says:

The value NIL is not of type FUNCTION.
   [Condition of type TYPE-ERROR]

Restarts:
 0: [RETRY] Retry SLIME REPL evaluation request.
 1: [*ABORT] Return to SLIME's top level.
 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {10033F8211}>)

Backtrace:
  0: (SB-DI:FUN-DEBUG-FUN NIL)[:EXTERNAL]
  1: (SB-DEBUG::TRACE-1 MOOSE #<SB-DEBUG::TRACE-INFO NIL> NIL)
  2: (SB-DEBUG::TRACE-1 MOOSE #<SB-DEBUG::TRACE-INFO NIL>)[:EXTERNAL]
  3: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SB-DEBUG::TRACE-1 'MOOSE '#<SB-DEBUG::TRACE-INFO NIL>) #<NULL-LEXENV>)
  4: (SB-INT:SIMPLE-EVAL-IN-LEXENV (LIST (SB-DEBUG::TRACE-1 'MOOSE '#<SB-DEBUG::TRACE-INFO NIL>)) #<NULL-LEXENV>)
  5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (TRACE MOOSE) #<NULL-LEXENV>)
  6: (EVAL (TRACE MOOSE))
 --more--

It would be nice if SBCL had a clearer error message about what had gone wrong.

This is with SBCL 1.0.46.42 on x86-64/darwin/macos-10.6.7

Nikodemus Siivola (nikodemus) wrote :

Fix waiting for 1.0.47 to be released.

Changed in sbcl:
assignee: nobody → Nikodemus Siivola (nikodemus)
importance: Undecided → Low
status: New → Triaged
Nikodemus Siivola (nikodemus) wrote :

1.0.47.2

Changed in sbcl:
assignee: Nikodemus Siivola (nikodemus) → nobody
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