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

fix Issue 19086 - Bad stack trace for exceptions #8937

Merged
merged 2 commits into from Nov 11, 2018

Conversation

rainers
Copy link
Member

@rainers rainers commented Nov 10, 2018

When building with debug info, add ud2 instruction after call to functions that never return. This allows the stack walker to find the correct source line

When building with debug info, add ud2 instruction after call to functions that never return. This allows the stack walker to find the correct source line
@dlang-bot
Copy link
Contributor

Thanks for your pull request, @rainers!

Bugzilla references

Auto-close Bugzilla Severity Description
19086 normal Bad stack trace for exceptions

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub fetch digger
dub run digger -- build "master + dmd#8937"

@thewilsonator
Copy link
Contributor

Hmm, freeBSD seems to have died.

@dlang-bot dlang-bot merged commit 01aec09 into dlang:master Nov 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants