Bug 2052982
Summary: | ppc64le: lldb loses connection with lldbserver | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Jesus Checa <jchecahi> | |
Component: | lldb | Assignee: | Timm Bäder <tbaeder> | |
Status: | CLOSED ERRATA | QA Contact: | Jesus Checa <jchecahi> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 9.0 | CC: | fweimer, mprchlik, sipoyare, tbaeder, tstellar | |
Target Milestone: | rc | Keywords: | Bugfix, Triaged, ZStream | |
Target Release: | --- | |||
Hardware: | ppc64le | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | lldb-14.0.0-1.el9 | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2079140 (view as bug list) | Environment: | ||
Last Closed: | 2022-11-15 10:19:00 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2079140 |
Description
Jesus Checa
2022-02-10 11:51:05 UTC
This is fixed in main and only happens when linking against the llvm dylib. I will try to bisect but the Beaker machine I got is pretty slow. Build lldb-14.0.0-1.el9 fixes the issue. Now lldb connects and debugs the target executable properly: + rpm -q --requires lldb python3-lldb + grep python3-lldb + g++ -g test.cpp + lldb -b -o 'breakpoint set --file test.cpp --line 7' -o run -o 'p v' -- a.out + tee lldb.log (lldb) target create "a.out" Current executable set to '/var/tmp/tmt/run-128/tests/build-gating/discover/lldb-upstream/tests/tests/python-embedded-interpreter/a.out' (powerpc64le). (lldb) breakpoint set --file test.cpp --line 7 Breakpoint 1: where = a.out`main + 108 at test.cpp:7:40, address = 0x0000000010000a38 (lldb) run Process 36322 stopped * thread #1, name = 'a.out', stop reason = breakpoint 1.1 frame #0: 0x0000000010000a38 a.out`main at test.cpp:7:40 4 main () 5 { 6 std::vector<int> v (1, 2); -> 7 std::vector<int>::iterator it(v.begin()); ^ 8 return 0; 9 } Process 36322 launched: '/var/tmp/tmt/run-128/tests/build-gating/discover/lldb-upstream/tests/tests/python-embedded-interpreter/a.out' (powerpc64le) (lldb) p v (std::vector<int, std::allocator<> >) $0 = size=1 { [0] = 2 } ++ grep -e '(std::vector<int, std::allocator<> >) $0 = size=1 {' -e '\[0\] = 2' lldb.log ++ wc -l + test 2 -eq 2 + rm lldb.log Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (llvm-toolset bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8092 *** Bug 2009469 has been marked as a duplicate of this bug. *** |