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.
This commit is contained in:
parent
92c2fe46e7
commit
b3fa4d069b
21 changed files with 957 additions and 118 deletions
16
tests/backtraces/call-with-resource-from-pool.scm
Normal file
16
tests/backtraces/call-with-resource-from-pool.scm
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
(use-modules (knots) (fibers) (knots resource-pool))
|
||||
|
||||
(run-fibers
|
||||
(lambda ()
|
||||
(let ((pool (make-resource-pool (const 'resource) 1)))
|
||||
;; FIRST BACKTRACE ENTRY: 1762:12 (with-exception-handler
|
||||
(with-exception-handler
|
||||
(lambda (e)
|
||||
(print-backtrace-and-exception/knots e)
|
||||
(primitive-exit 1))
|
||||
(lambda ()
|
||||
(call-with-resource-from-pool pool
|
||||
(lambda (resource)
|
||||
(error "error from call-with-resource-from-pool"))))))) ; LAST BACKTRACE ENTRY HERE
|
||||
#:hz 0 #:parallelism 1)
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue