The Common Lisp Condition System is my first book and it was previously discussed on Hacker News[0] as soon as the Apress page for the book was first posted.
The HN discussion was very fruitful and insightful and prompted me to add more content about the condition system in general. Due to time constraints and the flow of working on the book, it was impossible to add this new stuff to the actual body of the book, so me and Apress have decided to publish this content as an appendix named Discussing the Common Lisp Condition System and release it[1] on the Internet. The appendix is free to download and use in any way and I'd like to once again thank everyone who participated in the original thread.
The book is currently available for purchase on Apress[2] (with chapter samplers) and Amazon[3].
The full source code is available on GitHub[4] and should be buildable under any conforming C compilers and any conforming Common Lisp implementations. I'm available for answering any questions about it and merging any PRs that might arrive.
I hope that the book is helpful in general and wish everyone who decides to try it a good read.
Thanks. The only thing that is sad to me is that this content did not make it into the book itself.
(I guess that I can be proud of myself though: the first edition of the book wasn't even out of production and I already had some stuff written for the second edition.)
Yes, this last fact is explicitly mentioned in the last two sentences of this section.
> Another issue is preserving the state of the program stack, as it is destroyed in the process of dumping the Lisp image, and it cannot be fully restored when the image is thawed. However, portability libraries such as Dissect[0] allow for saving the stack state as normal Lisp data that can then be inspected using the system inspector.
Still, you can fully preserve the full stack information as Lisp data along with the whole heap, dump the image, and then inspect the dumped core as if you inspected any other Lisp image. This is already a big quality improvement over digging in dead crash dumps or - worse - textual, printed stacktraces with no other information available.
Therefore, I think that the statement "you can't use saved images to debug errors in SBCL" is somewhat far-fetched, really.
The Common Lisp Condition System is my first book and it was previously discussed on Hacker News[0] as soon as the Apress page for the book was first posted.
The HN discussion was very fruitful and insightful and prompted me to add more content about the condition system in general. Due to time constraints and the flow of working on the book, it was impossible to add this new stuff to the actual body of the book, so me and Apress have decided to publish this content as an appendix named Discussing the Common Lisp Condition System and release it[1] on the Internet. The appendix is free to download and use in any way and I'd like to once again thank everyone who participated in the original thread.
The book is currently available for purchase on Apress[2] (with chapter samplers) and Amazon[3].
The full source code is available on GitHub[4] and should be buildable under any conforming C compilers and any conforming Common Lisp implementations. I'm available for answering any questions about it and merging any PRs that might arrive.
I hope that the book is helpful in general and wish everyone who decides to try it a good read.
AMA.
[0] https://news.ycombinator.com/item?id=23843525
[1] https://github.com/Apress/common-lisp-condition-system/blob/...
[2] https://www.apress.com/us/book/9781484261330
[3] https://www.amazon.com/Common-Lisp-Condition-System-Mechanis...
[4] https://github.com/Apress/common-lisp-condition-system