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
runtime: TestLldbPython fails for lldb 7.0.0 #29244
Comments
Related to #22299 which fails for older lldb versions. But this one seems to fail even for new ones. |
Hmm. I poked at this for a while but never go to the point where the test could run on my machine (some bad combination of python, lldb, and python-lldb bindings config I assume). I get:
This is with "sudo apt-get install lldb-7 python-lldb-7" to install the basics. Is there a trick that I am missing? |
@thanm Given the name apt-get, I assume you're on a Debian or Ubuntu system? Which revision? I'm on Fedora 29 so I'll need to spin up a VM if I am to try and replicate the issue on another distro. |
Yes, I am using a Debian variant. Thanks for the offer of additional testing, but I'd like to discuss the test with a couple of my team-mates first. Looking at the test it's not clear to me exactly what it is supposed to be verifying. If the goal is only to check whether lldb can set a breakpoint on the toy program, then it might better just to run lldb in batch mode as opposed to via the python interface. Stay tuned. |
@jimrobinson I did manage to get my version 7 lldb + python-lldb installation issues resolved, so I can run test locally, including your debug script -- however I can't seem to reproduce the same bad behavior on my end (I do see the correct stop reason). I'll poke at it some more later today. |
@thanm thank you. So can we verify our respective setups?
The libraries python2 links against:
The libraries lldb links against:
|
@thanm, should this be milestoned to 1.12, 1.13, or Unplanned? |
At this point I am 99% sure it is a problem with the test, not with the Go compiler or DWARF. I'll put it in 1.13 |
This didn't used to happen to me in the same environment (Fedora 29 with lldb available), but something changed recently and I'm now getting this exact failure. A potentially relevant piece of information is that I recently applied a Fedora update that updated llvm but not lldb. It was apparently a minor rebuild that only changed the RPM version number (7.0.1-1 to 7.0.1-2), but maybe something gets perturbed even then. |
After some more investigation, I've established that what causes this test to start failing for me is switching from Fedora' earlier kernels (up through 4.19.15) to their 4.20.x kernel (either 4.20.3 or 4.20.4 so far). In 4.20.x, the Python script sees lldb stopping at the correct line but with reason eStopReasonNone. This also happens for a version of the test program built with Go 1.11, not just the latest go tip version, and also with Go 1.10 if I remove the Running lldb by hand on
The actual hit breakpoint only shows up if I list all threads:
If I Using the same compiled
(Since I ran into this myself, a note for people trying to reproduce this: if you extract the |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputThis is a Fedora 29 machine, it has lddb 7.0.0-1 and python2 2.7.15 installed:
What did you do?
$ cd /usr/local/go/src
$ git rev-parse HEAD
a629399
$ export GOROOT_BOOTSTRAP=/usr/local/lib/go1.11.2
$ ./all.bash
What did you expect to see?
What did you see instead?
It appears that the lldb script.py is not returning the expected output:
Digging it, this section of script.py is failing because the stop reason is not the expected value:
I added some debugging:
and this produces output indicating "Signal" and "None" stopped reasons:
TestLldbPython.debug.tar.gz
The text was updated successfully, but these errors were encountered: