Before I dive into the code to see if there's a bug, I wanted to see if I
was just doing it wrong.
I have an application with a different libc, etc than the machine I'm
running the debugger on. The application also has a bunch of libraries
that simply don't exist in the normal location on my dev
> On May 4, 2017, at 7:15 AM, Scott Smith via lldb-dev
> wrote:
>
> I would like to change the list of threads that lldb presents to the user for
> an internal application (not to be submitted upstream). It seems the right
> way to do this is to write an OperatingSystem plugin.
>
> 1. Can I
I would like to change the list of threads that lldb presents to the user
for an internal application (not to be submitted upstream). It seems the
right way to do this is to write an OperatingSystem plugin.
1. Can I still make it so the user can see real threads as well as whatever
other "threads
https://bugs.llvm.org/show_bug.cgi?id=32920
Bug ID: 32920
Summary: Potentially premature destroying of the locker in
Python interpreter
Product: lldb
Version: 3.9
Hardware: PC
OS: Windows NT
Stat
