clayborg wrote: > @jimingham , @clayborg, do you guys prefer `target stop-hook` style approach > or `SBNotificationCallback` style python API callback? > > @clayborg, for `SBNotificationCallback`, does `lldb::SBExecutionContext` wrap > the process, target or debugger object that is creating/destroying?
`lldb::SBExecutionContext` has target, process, thread and frame, but not debugger. We could add the `lldb::SBDebugger` to the `lldb::SBExecutionContext` if we want to avoid passing both the `lldb::SBDebugger' and the 'lldb::SBExecutionContext'. But right now `lldb::SBExecutionContext` doesn't have a debugger. But using `lldb::SBExecutionContext` will allow us to make notifications for just about anything (debugger, target, process, thread, frame lifetime events). https://github.com/llvm/llvm-project/pull/111206 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
