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

Expected uncaught exception in backtrace test #5806

Closed
vicuna opened this issue Nov 1, 2012 · 1 comment
Closed

Expected uncaught exception in backtrace test #5806

vicuna opened this issue Nov 1, 2012 · 1 comment
Labels

Comments

@vicuna
Copy link

@vicuna vicuna commented Nov 1, 2012

Original bug ID: 5806
Reporter: michi
Assigned to: @xclerc
Status: closed (set by @xavierleroy on 2015-12-11T18:08:18Z)
Resolution: fixed
Priority: low
Severity: trivial
Platform: amd64
OS: FreeBSD
OS Version: 9.0
Version: 4.00.1
Category: ~DO NOT USE (was: OCaml general)

Bug description

The testsuite challenges the backtrace capability of OCaml (testsuite/tests/backtrace). The challenge "b" causes the "program" to fail with an uncaught exception (exit code 2).

On my platform, this breaks the executions of the test script and GNU Make 3.82 abandons the target without comparing results with references, neither for "b" nor for "c", "d" and "". (See corresponding Makefile.)

Quite interestingly, this is not reported as a failed test by the test suite.

I am not very knowledgeable about GNU Make but I found out that the exit code of "program" could be hidden by replacing the faulty

OCAMLRUNPARAM=b=1 $(EXECNAME) $$arg

by

sh -c "OCAMLRUNPARAM=b=1 $(EXECNAME) $$arg; true"

in testsuite/tests/backtrace/Makefile.

@vicuna
Copy link
Author

@vicuna vicuna commented Nov 5, 2012

Comment author: @xclerc

Fixed in both trunk (revision 13062), and '4.00' (revision 13063) branches.

@vicuna vicuna closed this Dec 11, 2015
@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
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant