-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
LLDB does not flush IO after expression evaluation which makes output of expression overlapped #110528
Comments
@llvm/issue-subscribers-lldb Author: zhq (ikey4u)
When debugging clang static analyzer, the output of evaluating dump of ProgramState of ExplodedNode seems does not work in LLDB, the issue is weirded that I cannot describe it in simple one or two statements. As a result, I spend a lot of time to create a docker environment that easy you to reproduce the problem, and the problem is described in the last.
HostThe following operations are executed in host.
DockerThe following operations are executed in docker, you can use following command
|
This is a great report thankyou! I am just back from vacation, so it will be a few days until I can look into this. |
When debugging clang static analyzer, the output of evaluating dump of ProgramState of ExplodedNode seems does not work in LLDB, the issue is weirded that I cannot describe it in simple one or two statements. As a result, I spend a lot of time to create a docker environment that easy you to reproduce the problem, and the problem is described in the last.
Host
The following operations are executed in host.
Create docker base image
Create docker container
Docker
The following operations are executed in docker, you can use following command
to get into docker on your host:
Update yum
Install dependencies
Build lldb
The time has finally come to reproduce the bug
Create a div zero file in home directory:
Load it using lldb:
Disable ASLR in lldb when using lldb in a docker to avoid error
personality set failed: Operation not permitted
:And set a breakpoint in lldb:
Then run lldb:
When the breakpoint hits, checke the ExplodeNode state using following
command:
Note that lldb auto fix the command, and let's type the right command, the
bug appears:
Note that the last
(lldb)
which is not right, and the content between thetwo
(lldb)
will not appear correctly on the terminal which seems is eatout by the terminal.
The text was updated successfully, but these errors were encountered: