This patch introduces a new option for the interactive crashlog mode,
that will prevent it from dumping the process status & thread backtrace
output to the debugger console.
This is necessary when lldb in running from an IDE, to prevent flooding
the console with information that should be already present in the UI.
rdar://96813296
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
Is there another way to detect that we're running in this kind of environment? For example, could we check if we're in an interactive lldb session? I imagine you'd like to have the same behavior as the IDE case if you imported the crashlog module in another Python file for example. One easy way to determine this is to check if lldb.debugger exists, but I'm not sure if that will cover the IDE case you're trying to solve.