@tbaeder I tested build lldb-13.0.1-2.el9_0 using compose RHEL-9.0.0-updates-20220526.0. The issue still persists:

// -- test.cpp --
#include <stdio.h>
#include <vector>
int
main ()
{
  std::vector<int> v (1, 2);
  std::vector<int>::iterator it(v.begin());
  return 0;
}
// --------------

+ 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-231/tests/build-gating/discover/lldb-tests/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 22558 exited with status = -1 (0xffffffff) lost connection
Process 22558 launched: '/var/tmp/tmt/run-231/tests/build-gating/discover/lldb-tests/tests/tests/python-embedded-interpreter/a.out' (powerpc64le)

Build lldb-13.0.1-3.el9_0 now fixes the issue. Verified that lldb now runs as intended in ppc64le.

No regressions observed in any supported arch.

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 (lldb 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:5262