Merge pull request #22 from 40ants/fix-unreadable-objects

Fixed error on printing a backtrace when *PRINT-READABLY* is T

Author: svetlyak40wt

src/changelog.lisp

@@ -19,6 +19,20 @@
                               "HTTP"
                               "ASDF"
                               "TRACEBACK-TO-STRING"))
+  (0.11.1 2025-10-05
+          "
+## Fixed
+
+Previously you may encounter this sort of errors when trying to get a backtrace or use LOG4CL-EXTRAS/ERROR:WITH-LOG-UNHANDLED macro:
+
+```
+Traceback (most recent call last):\n[unable to format because of Unable to get traceback because of another error during printing:\n#<PRINT-NOT-READABLE {1213990E43}> cannot be printed readably.\"},\"level\":\"ERROR\",\"message\":\"Unhandled exception\",\"timestamp\":\"2025-10-05T16:23:40.869358Z\"
+```
+
+This error occured when `*print-readably*` variable was bound to `T`.
+
+Now LOG4CL-EXTRAS/ERROR:PRINT-BACKTRACE function binds `*print-readably*` to `NIL` when rendering a backtrace. This might change how do your backtraces look like.
+")
   (0.11.0 2024-03-01
           "
 ## Changed

src/error.lisp

@@ -307,7 +307,8 @@ how to not log secret values.
    But you can change this by providing an argument FORMAT-CONDITION. It should be a
    function of two arguments: `(stream condition)`.
    "
-  (let ((frames (get-backtrace)))
+  (let* ((frames (get-backtrace))
+         (*print-readably* nil))
     (with-output-to-stream (stream stream)
       (handler-case
           (progn