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
Uncaught exceptions in start { } blocks get no backtrace when raised via await #4464
Comments
From @hoelzroSee the attached script. The original backtrace of an exception seems to vanish when awaiting a Promise throws that exception. |
From @hoelzroOn 2015-08-10 14:20:34, rob@hoelz.ro wrote:
Forgot the script! |
From @jnthnOn Mon Aug 10 14:20:34 2015, rob@hoelz.ro wrote:
Now we show both backtraces, and more clearly explain what happened (that we're throwing now because the result of a broken Promise was requested, followed by the original exception that broke the Promise and its location). Test in S17-promise/start.t. /jnthn |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125782 (status was 'resolved')
Searchable as RT125782$
The text was updated successfully, but these errors were encountered: