From 7a5014b04057f9f471d6977a98cc6a87d5a9e484 Mon Sep 17 00:00:00 2001 From: Jason Molenda Date: Wed, 1 Apr 2015 02:09:04 +0000 Subject: [PATCH] Add a call to SBDebugger:Destroy() at the end of the self-hosted version of this script. We picked up a bug at some point in March where scripts that fail to call SBDebugger::Destroy() will crash in the Debugger C++ dtor. I want to track the change down which introduced the change - but this script should be calling SBDebugger::Destroy() in the first place, so do that. llvm-svn: 233779 --- lldb/examples/python/crashlog.py | 1 + 1 file changed, 1 insertion(+) diff --git a/lldb/examples/python/crashlog.py b/lldb/examples/python/crashlog.py index 52ffb78d4419..403b92f353f7 100755 --- a/lldb/examples/python/crashlog.py +++ b/lldb/examples/python/crashlog.py @@ -820,6 +820,7 @@ if __name__ == '__main__': # Create a new debugger instance lldb.debugger = lldb.SBDebugger.Create() SymbolicateCrashLogs (sys.argv[1:]) + lldb.SBDebugger.Destroy (lldb.debugger) elif getattr(lldb, 'debugger', None): lldb.debugger.HandleCommand('command script add -f lldb.macosx.crashlog.Symbolicate crashlog') lldb.debugger.HandleCommand('command script add -f lldb.macosx.crashlog.save_crashlog save_crashlog')