guile-knots/tests/backtraces/fibers-force.scm

(use-modules (knots) (fibers) (knots promise))

(run-fibers
 (lambda ()
   ;; FIRST BACKTRACE ENTRY: (with-exception-handler
   (with-exception-handler
       (lambda (e)
         (print-backtrace-and-exception/knots e)
         (primitive-exit 1))
     (lambda ()
       (fibers-force
        (fibers-delay
         (lambda ()
           (error "error from fibers-force"))))))) ; LAST BACKTRACE ENTRY HERE
 #:hz 0 #:parallelism 1)
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) (fibers) (knots promise))`

			`(run-fibers`
			`(lambda ()`
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 (e)`
			`(print-backtrace-and-exception/knots e)`
			`(primitive-exit 1))`
			`(lambda ()`
			`(fibers-force`
			`(fibers-delay`
			`(lambda ()`
			`(error "error from fibers-force"))))))) ; LAST BACKTRACE ENTRY HERE`
			`#:hz 0 #:parallelism 1)`