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
[SR-11746] lldb on Linux (Swift 5.1.2): lldb crash with {{e ev}} #4435
Comments
@swift-ci create |
CC @dcci / @adrian-prantl / friss (JIRA User) |
@augusto2112 if you want another bug to look at – this might be a good one. |
I'll take a look! |
Bug fixed here |
Awesome, thanks @augusto2112. Just tried with the latest master snapshot where it still crashes but I reckon this will take another day to hit the swift master snapshot. Here's the one-line to repro it with latest master:
|
@augusto2112 should it be working with the latest master snapshot of today or do I need to wait for tomorrow? Just tested it and right now it still fails. I'm running
|
Hi @weissi, Hmm, yeah, I wasn't recompiling swift-nio, so running the newest lldb on the already compiled code works as expected, but if I re-clone and re-compile with the latest swift version the debugger goes back to crashing, weird... I'll take a second look on why this is still happening, sorry for the mistake. |
Thanks so much @augusto2112! |
@augusto2112 how cool and thanks so much, will monitor that PR and retest with the snapshot once that's in too 🙂 |
Hi @weissi. The bug is (finally!) fixed. I've tested with the latest snapshot just to make sure everything is working correctly 🙂 |
@augusto2112 You're a star! Thank you. I can confirm it works on master. Proof:
|
Additional Detail from JIRA
md5: 998cf315c6e314400034365f07f267e8
Issue Description:
Description
When running the following 1 liner (runnable from macOS (with Docker for Mac installed) or Linux) I get an lldb crash.
which can also be broken into multiple lines:
once
lldb
is started, please typeOnce lldb has hit the breakpoint, run
and you'll see the output
The text was updated successfully, but these errors were encountered: