Thank you Pavel! That's interesting.
Not that urgent, I have a workaround for this issue. For the inferior, I
just copied some random multithreading code from internet to demonstrate
this issue, definitely a good way exit main thread :-).
Btw: I was surprised on Mac/Linux the whole process is still
https://llvm.org/bugs/show_bug.cgi?id=27227
Adrian McCarthy changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hello,
I've been working on adding support for Linux on SystemZ as a target (and
host) platform for LLDB, and now have a patch set ready that I'd like to
submit for upstream inclusion.
For reference, I've attached the patch set as a quilt stack.
(See attached file: patches-lldb-s390x.tar.bz2)
I
Ok, so the reason for this behavior seems to be that the process hits
two breakpoints simultaneously:
- the breakpoint you have set and you are expecting to hit
- an internal shared library breakpoint we use to get notified of new
shared libraries
* thread #1: tid = 33390, 0x7ff7dcd9f970
ld-li
