guile-knots/tests/backtraces/triple-with-exception-handler.scm

(use-modules (knots))

;; FIRST BACKTRACE ENTRY: (with-exception-handler

(with-exception-handler
    (lambda _ #f)
  (lambda ()
    (with-exception-handler
        (lambda _ #f)
      (lambda ()
        (with-exception-handler
            (lambda (exn)
              (print-backtrace-and-exception/knots exn)
              (primitive-exit 1))
          (lambda ()
            (error "plain error message"))))))) ; LAST BACKTRACE ENTRY HERE
Rework the backtrace handling Try and improve the print-backtrace-and-exception/knots output, be selective about the stack frames which are shown to try and produce some useful output which reflects user code and hide the &knots-exceptions. This commit also introduces a bunch of tests scripts that produce output from print-backtrace-and-exception/knots, to help test this code in different situations. 2026-03-20 19:11:03 +00:00			`(use-modules (knots))`

Remove Guile line numbers from backtrace tests As these differ between 3.0.10 and 3.0.11. 2026-03-22 19:12:59 +00:00			`;; FIRST BACKTRACE ENTRY: (with-exception-handler`
Rework the backtrace handling Try and improve the print-backtrace-and-exception/knots output, be selective about the stack frames which are shown to try and produce some useful output which reflects user code and hide the &knots-exceptions. This commit also introduces a bunch of tests scripts that produce output from print-backtrace-and-exception/knots, to help test this code in different situations. 2026-03-20 19:11:03 +00:00
			`(with-exception-handler`
			`(lambda _ #f)`
			`(lambda ()`
			`(with-exception-handler`
			`(lambda _ #f)`
			`(lambda ()`
			`(with-exception-handler`
			`(lambda (exn)`
			`(print-backtrace-and-exception/knots exn)`
			`(primitive-exit 1))`
			`(lambda ()`
			`(error "plain error message"))))))) ; LAST BACKTRACE ENTRY HERE`