Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I use the --load option to run a program which may signal an error.
The program sets up restarts so that I can interactively choose how to
deal with the error, but these are lost when I arrive at the debugger.
The reason for this is that the function SB-IMPL::PROCESS-EVAL-OPTIONS
tries to be "helpful" by setting up a handler which signals yet
another error. In doing this, the handler does not decline to handle
the condition, and so the restarts established up to that point are no
One possible solution is to set up a restart within the handler that,
when invoked, will cause the handler to decline (the perfect job for
Another solution is to remove the handler altogether. I prefer this
solution, as I think the restarts established by PROCESS-EVAL-OPTIONS
are sufficiently helpful.
I also noticed a similarly "helpful" handler in the function