-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backtraces appear to be broken. #171
Comments
Backtraces extracted from the native stack don't make sense in a concurrency monad (computations are captured and usually reinstantiated in a totally different context; here the scheduler as shown by lines referring to I made a proof of concept of backtrace-aware lwt but it is left in a broken state at the moment (you'll need a specific version of owee and it'll work only on amd64 linux). |
Just to clarify, what I'm seeing is expected ?
|
Yup you're correct, I forgot about the syntax extension which I didn't use for a long time. |
Try it with ocaml 4.01. There is an open bug report around this issue: http://caml.inria.fr/mantis/view.php?id=6556 |
I can't seem to get traces to work correctly, the trace is incomplete does not show the module that generated an exception, first I was generating a normal exception than I was told I needed to Lwt.wrap it, still have the same behaviour, this is the backtrace I get:
Fatal error: exception Failure("boom")
Raised at file "src/core/lwt.ml", line 788, characters 22-23
Called from file "src/unix/lwt_main.ml", line 34, characters 8-18
No line for the Boom.crash() call.
Called from file "exc.ml", line 13, characters 2-26 (This is the Lwt_main.run)
On my original case I don't even get the bottom line, my trace starts at lwt_main.ml line 34.
exc.ml:
boom.ml:
here is the _log build:
The text was updated successfully, but these errors were encountered: