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

Improve the printing of exceptions (pp registered) #6301

Closed
vicuna opened this issue Jan 20, 2014 · 3 comments
Closed

Improve the printing of exceptions (pp registered) #6301

vicuna opened this issue Jan 20, 2014 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Jan 20, 2014

Original bug ID: 6301
Reporter: @Chris00
Status: acknowledged (set by @damiendoligez on 2014-07-16T11:44:33Z)
Resolution: open
Priority: normal
Severity: minor
Platform: x86_64
OS: GNU/Linux
OS Version: 3.10.25
Version: 4.01.0
Category: standard library
Monitored by: @dbuenzli

Bug description

The documentation of Printexc.catch says it is deprecated because "the runtime system is now able to print uncaught exceptions as precisely as [Printexc.catch] does". However, that is not entirely true (even) when exception pp are registered. On my machine, the attached code prints:

Uncaught exception: Err.E(A)
Fatal error: exception Err.E(0)

File attachments

@vicuna
Copy link
Author

vicuna commented Jan 20, 2015

Comment author: @damiendoligez

Maybe we should just un-deprecate Printexc.catch.

Having the runtime's generic exception printer call back to user code seems like a lot of trouble.

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 13, 2020
@xavierleroy
Copy link
Contributor

Having the runtime's generic exception printer call back to user code seems like a lot of trouble.

Someone took that trouble: #5941 . The test now produces the expected result.

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

2 participants