From c5041918dda38fbb480ce73da2784ae4765171d3 Mon Sep 17 00:00:00 2001 From: Filipe Cabecinhas Date: Sat, 25 Aug 2012 00:29:07 +0000 Subject: Added SBDebugger's log callbacks to Python-land - Tweaked a parameter name in SBDebugger.h so my typemap will catch it; - Added a SBDebugger.Create(bool, callback, baton) to the swig interface; - Added SBDebugger.SetLoggingCallback to the swig interface; - Added a callback utility function for log callbacks; - Guard against Py_None on both callback utility functions; - Added a FIXME to the SBDebugger API test; - Added a __del__() stub for SBDebugger. We need to be able to get both the log callback and baton from an SBDebugger if we want to protect against memory leaks (or make the user responsible for holding another reference to the callback). Additionally, it's impossible to revert from a callback-backed log mechanism to a file-backed log mechanism. llvm-svn: 162633 --- lldb/scripts/Python/interface/SBDebugger.i | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'lldb/scripts/Python/interface/SBDebugger.i') diff --git a/lldb/scripts/Python/interface/SBDebugger.i b/lldb/scripts/Python/interface/SBDebugger.i index 883ed1c5fb5..a27d280de7e 100644 --- a/lldb/scripts/Python/interface/SBDebugger.i +++ b/lldb/scripts/Python/interface/SBDebugger.i @@ -122,6 +122,9 @@ public: static lldb::SBDebugger Create(bool source_init_files); + static lldb::SBDebugger + Create(bool source_init_files, lldb::LogOutputCallback log_callback, void *baton); + static void Destroy (lldb::SBDebugger &debugger); @@ -271,6 +274,9 @@ public: bool EnableLog (const char *channel, const char ** types); + void + SetLoggingCallback (lldb::LogOutputCallback log_callback, void *baton); + void DispatchInput (const void *data, size_t data_len); -- cgit v1.2.3