[Lldb-commits] [PATCH] D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP]

mgorny updated this revision to Diff 213231. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D6/new/ https://reviews.llvm.org/D6 Files: lldb/packages/Python/lldbsuite/test/functionalities/thread/concurrent_events/TestConcurrentBreakpointOneDelayBreakpointThreads.py lldb/packag

[Lldb-commits] [PATCH] D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP]

mgorny marked 6 inline comments as done. mgorny added a comment. @jfb, could you please remove your red flag now? ;-) Comment at: lldb/source/Plugins/Process/NetBSD/NativeProcessNetBSD.cpp:738 +if (*it && ((*it)->GetID() == thread_id)) { + m_threads.erase(it); + b

[Lldb-commits] [PATCH] D65691: Various build fixes for lldb on MinGW

xbolva00 added inline comments. Comment at: lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp:19 #endif +#ifdef __MINGW32__ +// usleep Maybe drop usleep and use C++’s https://en.cppreference.com/w/cpp/thread/sleep_for ? Repository: rG LLVM Github

[Lldb-commits] [PATCH] D65691: Various build fixes for lldb on MinGW

clayborg added a comment. In D65691#1613395 , @mstorsjo wrote: > As context (I haven't followed lldb almost at all), what's the general status > of lldb on windows - generally working, or still a work in progress? Does it > work with dwarf debug info in