Closed artagnon closed 4 months ago
This seems to be a regression in the latest version of lldb, or a bug in the printer, and I'm able to reproduce the issue on iTerm. Sorry for the noise.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240520-135708-b8f94c47
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
It's hard to explain exactly, but I've recorded the buggy lldb session here:
https://asciinema.org/a/ST2nBRj5Lk1mSDS65UXeoK61O
Basically, once a
print
command is invoked, it should print the result before showing the(lldb)
prompt again. Instead, it has polluted the(lldb)
prompt with the output.The bug is very debilitating, and is a major blocker for any C/C++ development. I will have to switch back to iTerm until this bug is resolved.
To Reproduce
Attempt to dump a string in lldb.
Configuration
Expected Behavior
Print the lldb output on a separate line, before giving the next
(lldb)
prompt.Logs
wezterm version: 20240520-135708-b8f94c47 aarch64-apple-darwin Window Environment: macOS 14.5 (23F79) Lua Version: Lua 5.4 OpenGL: Apple M2 4.1 Metal - 88.1
Anything else?
No response