> could you get a backtrace of lldb-server when it is in the "stuck"
state (just attach with lldb/gdb after it hangs and do "bt")?
You wish [☹] The lldb-server does not react to any signals including SIGSTOP,
so gdb just hangs forever.
> If you can get me reasonably detailed repro steps, I c
https://llvm.org/bugs/show_bug.cgi?id=31308
Bug ID: 31308
Summary: po sometimes prints blank instead of object
Product: lldb
Version: 3.6
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: normal
Sorry, I have been derailed today by trying to make format member
detection work more reasonably. I plan to come up with the next
iteration of the proposal soon, but I am not sure if it will be today,
as it is quite late here already. I do think this needs to be done in
incremental steps, but I'd l
Pavel: You might start this effort to improve logging by just adding a
Formatv member function to log to replace printf.
I suspect many call sites would be made much less verbose this way. I think
we'll still need to do the rest too, but this seems like the least amount
of work to make incremental
Hello Eugene,
this sounds troubling, and I'd like to get to the bottom of this. If
you can get me a bit more information about this, I believe we can
figure it out:
- could you get a backtrace of lldb-server when it is in the "stuck"
state (just attach with lldb/gdb after it hangs and do "bt")? I
