[Lldb-commits] [lldb] Add a test for evicting unreachable modules from the global module cache (PR #74894)

[via lldb-commits]

jimingham wrote:

This can happen if you don't succeed in shutting down the private state thread as part of exiting, so that it is still trying to operate on a process that has been finalized.

Not sure why the shutdown ordering seems wrong in the Linux case, however.

Jim


> On Dec 15, 2023, at 1:39 AM, David Spickett ***@***.***> wrote:
> 
> 
> Though the original assert was: m_plans.size() > 1 && "Can't pop the base thread plan"
> 
> Not that there was exactly 1 plan on the stack. So current_plan might be the single step plan as expected, then when we go to pop that off the stack, but the stack has been emptied/destroyed already.
> 
> —
> Reply to this email directly, view it on GitHub <https://github.com/llvm/llvm-project/pull/74894#issuecomment-1857567808>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUPVWY52KBS5JSVF5J6JTDYJQLFBAVCNFSM6AAAAABANJIUI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGU3DOOBQHA>.
> You are receiving this because you modified the open/close state.
> 



https://github.com/llvm/llvm-project/pull/74894