wanted: better error reporting on errors during LOAD and evaluation of top-level forms

Bug #565247 reported by Tobias C. Rittweiler on 2010-04-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Wishlist
Unassigned

Bug Description

(in-package :cl-user)

(defclass foo ()
  ((name :reader name)))

(defvar *foo* nil)

(defun foo (x)
  (1+ x))

(name *foo*)

(defun bar (y)
  (1- y))

LOADing that file results in

There is no applicable method for the generic function
  #<STANDARD-GENERIC-FUNCTION NAME (1)>
when called with arguments
  (NIL).
   [Condition of type SIMPLE-ERROR]

Restarts:
 0: [RETRY] Retry calling the generic function.
 1: [ABORT] Abort compilation.
 2: [ABORT] Return to SLIME's top level.
 3: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker" RUNNING {CCD6689}>)

Backtrace:
  0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION NAME (1)>)[:EXTERNAL]
  1: (SB-PCL::CALL-NO-APPLICABLE-METHOD #<STANDARD-GENERIC-FUNCTION NAME (1)> (NIL))
  2: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file /tmp/foo.fasl" {B0AE541}>)

Now imagine that the actual file is large. Would be nice if the error included
the toplevel number, or an actual character offset...

Changed in sbcl:
importance: Undecided → Wishlist
status: New → Triaged
Douglas Katzman (dougk) on 2015-05-12
tags: added: reader
Douglas Katzman (dougk) on 2015-05-13
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