Assert failure does not print full stack trace

Hello all,

It seems when assertion failure is hit a portion of stack trace is optimized away.

ubuntu:~/ocaml-playground$ dune test                            
File "lib/Instr.ml", line 137, characters 2-71: <<true>> threw "Assert_failure lib/Util.ml:97:2".
  Raised at file "src/exn.ml", line 71, characters 4-114                                         
  Called from file "runtime-lib/runtime.ml", line 356, characters 15-52                          
  Called from file "runtime-lib/runtime.ml", line 444, characters 52-83                          
  in TEST_MODULE at file "lib/intro.ml", line 136, characters 0-110                              

The printed stack trace misses a few function calls.

Is there a way to fully print it?

Thanks!

4 posts - 3 participants

Read full topic