terrible error reporting when fasl-loading symbols in unknown packages
Bug #553943 reported by
Attila Lendvai
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Medium
|
Unassigned |
Bug Description
fasl loading doesn't report useful messages in case of errors.
a situation i've met several times: due to an accidental redefinition, a macro expansion contains symbols from packages that are not part of the dependency. then compiling a fasl will emit symbols in the fasl whose package is not available next time the library is loaded into a fresh VM.
in these situation fasl loading dies in find-undeleted-
Changed in sbcl: | |
status: | New → Confirmed |
summary: |
- wanted: better error reporting from fasl loading + wanted: better error reporting from fasl loading symbols in unknown + packages |
Changed in sbcl: | |
importance: | Undecided → Wishlist |
tags: | added: fasl |
Changed in sbcl: | |
importance: | Wishlist → Medium |
summary: |
- wanted: better error reporting from fasl loading symbols in unknown - packages + terrible error reporting when fasl-loading symbols in unknown packages |
Changed in sbcl: | |
status: | Confirmed → Triaged |
assignee: | nobody → Nikodemus Siivola (nikodemus) |
Changed in sbcl: | |
assignee: | Nikodemus Siivola (nikodemus) → nobody |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
To be really clever, one would modify the fasdumper to prepare a table of all symbols used in a particular package, so that it could dump them all at the same time, and use a single (new) FOP to load them all at once, which would lead to being able to say "the following symbols were dumped from missing package FOO...", but that's a lot more work to implement.