Skip to content
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 are concatenated when flambda turned on #7262

Closed
vicuna opened this issue May 20, 2016 · 1 comment
Closed

backtraces are concatenated when flambda turned on #7262

vicuna opened this issue May 20, 2016 · 1 comment

Comments

@vicuna
Copy link

vicuna commented May 20, 2016

Original bug ID: 7262
Reporter: mon
Status: closed (set by @mshinwell on 2016-12-08T11:31:50Z)
Resolution: duplicate
Priority: low
Severity: minor
Platform: amd64
OS: linux
Target version: 4.05.0 +dev/beta1/beta2/beta3/rc1
Category: runtime system and C interface
Monitored by: @gasche

Bug description

raising exception from C code concatenates backtrace with backtrace from previous raise if using 4.03.0+flambda

Steps to reproduce

$ opam switch 4.03.0; eval opam config env; make clean && make foo && ./foo
rm -f *.o *.cmx *.cmi foo
cc -c -o stub.o stub.c
ocamlopt stub.o foo.ml -o foo




$ opam switch 4.03.0+flambda; eval opam config env; make clean && make foo && ./foo

To setup the new switch in the current shell, you need to run:

eval opam config env
rm -f *.o *.cmx *.cmi foo
cc -c -o stub.o stub.c
ocamlopt stub.o foo.ml -o foo
Called from file "foo.ml", line 7, characters 10-16

Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16

Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16

Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16
Called from file "foo.ml", line 7, characters 10-16

File attachments

@vicuna
Copy link
Author

vicuna commented Dec 8, 2016

Comment author: @mshinwell

This not an Flambda problem, but instead relates to the fact that the second and subsequent raises are being treated as "re-raise".

Moved to #293 for further discussion.

@vicuna vicuna closed this as completed Dec 8, 2016
@vicuna vicuna added this to the 4.05.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant