FMAKUNBOUND a traced function makes UNTRACE signal an error
Bug #667657 reported by
Jānis Džeriņš
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Low
|
Unassigned |
Bug Description
Removing the global function definition from a traced symbol (function) makes
UNTRACE with no arguments (i.e., the intent being of untracing everything
that's being traced) to signal an UNDEFINED-FUNCTION error.
As it is now (SBCL 1.0.43.74), it is impossible to remove the funbound symbol
from the trace list.
If the same function is redefined and traced again, the same symbol is
inserted into the list of traced functions; calling UNTRACE with no arguments
now will warn about function being not traced. (What is a function that is
not being traced doing in the trace list, anyway?)
A sketch of the test case is attached.
Changed in sbcl: | |
status: | New → Fix Committed |
Changed in sbcl: | |
status: | Triaged → In Progress |
importance: | Undecided → Low |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Sorry for the misformatting, and I misunderstood the meaning of "this file is a patch", so, the attached file is a test case, not a patch.