summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python
Commit message (Collapse)AuthorAgeFilesLines
* Add a new breakpoint type "break by source regular expression".Jim Ingham2011-09-213-2/+49
| | | | | | | | | Fix the RegularExpression class so it has a real copy constructor. Fix the breakpoint setting with multiple shared libraries so it makes one breakpoint not one per shared library. Add SBFileSpecList, to be used to expose the above to the SB interface (not done yet.) llvm-svn: 140225
* Untabify and fix indentations. Tabs are bad.Johnny Chen2011-09-151-51/+51
| | | | llvm-svn: 139862
* Adding "-n", "-p" and "-w" flags to the lldb command-line tool toJim Ingham2011-09-131-0/+6
| | | | | | allow attaching from the command line. llvm-svn: 139665
* SBSourceManager now gets the real source manager either from the Debugger or ↵Jim Ingham2011-09-132-1/+4
| | | | | | | | Target. Also, move the SourceManager file cache into the debugger so it can be shared amongst the targets. llvm-svn: 139564
* Added the ability to introspect types thourgh the public SBType interface.Greg Clayton2011-09-092-32/+82
| | | | | | | | Fixed up many API calls to not be "const" as const doesn't mean anything to most of our lldb::SB objects since they contain a shared pointer, auto_ptr, or pointer to the types which circumvent the constness anyway. llvm-svn: 139428
* Fixed the error message:Johnny Chen2011-09-091-33/+33
| | | | | | | | ./build-swig-Python.sh: line 76: INTERFACE_FILES: command not found when running SWIG, which was introduced during the last checkin. llvm-svn: 139376
* Redesign of the interaction between Python and frozen objects:Enrico Granata2011-09-065-2/+215
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - introduced two new classes ValueObjectConstResultChild and ValueObjectConstResultImpl: the first one is a ValueObjectChild obtained from a ValueObjectConstResult, the second is a common implementation backend for VOCR and VOCRCh of method calls meant to read through pointers stored in frozen objects ; now such reads transparently move from host to target as required - as a consequence of the above, removed code that made target-memory copies of expression results in several places throughout LLDB, and also removed code that enabled to recognize an expression result VO as such - introduced a new GetPointeeData() method in ValueObject that lets you read a given amount of objects of type T from a VO representing a T* or T[], and doing dereferences transparently in private layer it returns a DataExtractor ; in public layer it returns an instance of a newly created lldb::SBData - as GetPointeeData() does the right thing for both frozen and non-frozen ValueObject's, reimplemented ReadPointedString() to use it en lieu of doing the raw read itself - introduced a new GetData() method in ValueObject that lets you get a copy of the data that backs the ValueObject (for pointers, this returns the address without any previous dereferencing steps ; for arrays it actually reads the whole chunk of memory) in public layer this returns an SBData, just like GetPointeeData() - introduced a new CreateValueFromData() method in SBValue that lets you create a new SBValue from a chunk of data wrapped in an SBData the limitation to remember for this kind of SBValue is that they have no address: extracting the address-of for these objects (with any of GetAddress(), GetLoadAddress() and AddressOf()) will return invalid values - added several tests to check that "p"-ing objects (STL classes, char* and char[]) will do the right thing Solved a bug where global pointers to global variables were not dereferenced correctly for display New target setting "max-string-summary-length" gives the maximum number of characters to show in a string when summarizing it, instead of the hardcoded 128 Solved a bug where the summary for char[] and char* would not be shown if the ValueObject's were dumped via the "p" command Removed m_pointers_point_to_load_addrs from ValueObject. Introduced a new m_address_type_of_children, which each ValueObject can set to tell the address type of any pointers and/or references it creates. In the current codebase, this is load address most of the time (the only notable exception being file addresses that generate file address children UNLESS we have a live process) Updated help text for summary-string Fixed an issue in STL formatters where std::stlcontainer::iterator would match the container's synthetic children providers Edited the syntax and help for some commands to have proper argument types llvm-svn: 139160
* Additional code cleanups ; Short option name for --python-script in type ↵Enrico Granata2011-08-231-2/+0
| | | | | | summary add moved from -s to -o (this is a preliminary step in moving the short option for --summary-string from -f to -s) ; Accordingly updated the test suite llvm-svn: 138315
* Check the timesatmps of includees python-extensions.swig and ↵Johnny Chen2011-08-221-4/+17
| | | | | | | | python-wrapper.swig and force a re-SWIG if newer than the SWIG-generated LLDBWrapPython.cpp file. llvm-svn: 138280
* - Support for Python namespaces:Enrico Granata2011-08-221-206/+133
| | | | | | | | | | | If you have a Python module foo, in order to use its contained objects in LLDB you do not need to use 'from foo import *'. You can use 'import foo', and then refer to items in foo as 'foo.bar', and LLDB will know how to resolve bar as a member of foo. Accordingly, GNU libstdc++ formatters have been moved from the global namespace to gnu_libstdcpp and a few test cases are also updated to reflect the new convention. Python docs suggest using a plain 'import' en lieu of 'from-import'. llvm-svn: 138244
* Further fix for SWIG interoperability; making sure the Release() method of ↵Enrico Granata2011-08-201-13/+30
| | | | | | SBCommandReturnObject is called at all times llvm-svn: 138169
* Fixed some SWIG interoperability issuesEnrico Granata2011-08-191-13/+26
| | | | llvm-svn: 138154
* Taking care of an issue with using lldb_private types in ↵Enrico Granata2011-08-191-2/+2
| | | | | | SBCommandInterpreter.cpp ; Making NSString test case work on Snow Leopard ; Removing an unused variable warning llvm-svn: 138105
* First round of code cleanups:Enrico Granata2011-08-171-5/+5
| | | | | | | | | | | | | | | | | | - all instances of "vobj" have been renamed to "valobj" - class Debugger::Formatting has been renamed to DataVisualization (defined in FormatManager.h/cpp) The interface to this class has not changed - FormatCategory now uses ConstString's as keys to the navigators instead of repeatedly casting from ConstString to const char* and back all the time Next step is making the same happen for categories themselves - category gnu-libstdc++ is defined in the constructor for a FormatManager The source code for it is defined in gnu_libstdcpp.py, drawn from examples/synthetic at compile time All references to previous 'osxcpp' name have been removed from both code and file names Functional changes: - the name of the option to use a summary string for 'type summary add' has changed from the previous --format-string to the new --summary-string. It is expected that the short option will change from -f to -s, and -s for --python-script will become -o llvm-svn: 137886
* New category "gnu-libstdc++" provides summary for std::string and synthetic ↵Enrico Granata2011-08-171-0/+15
| | | | | | | | | | children for types std::map, std::list and std::vector The category is enabled by default. If you run into issues with it, disable it and the previous behavior of LLDB is restored ** This is a temporary solution. The general solution to having formatters pulled in at startup should involve going through the Platform. Fixed an issue in type synthetic list where a category with synthetic providers in it was not shown if all the providers were regex-based llvm-svn: 137850
* Changes to Python commands:Enrico Granata2011-08-162-4/+13
| | | | | | | | | | | | - They now have an SBCommandReturnObject instead of an SBStream as third argument - The class CommandObjectPythonFunction has been merged into CommandObjectCommands.cpp - The command to manage them is now: command script with subcommands add, list, delete, clear command alias is returned to its previous functionality - Python commands are now part of an user dictionary, instead of being seen as aliases llvm-svn: 137785
* Python commands:Enrico Granata2011-08-161-0/+140
| | | | | | | | | | | | | It is now possible to use 'command alias --python' to define a command name that actually triggers execution of a Python function (e.g. command alias --python foo foo_impl makes a command named 'foo' that runs Python function 'foo_impl') The Python function foo_impl should have as signature: def foo_impl(debugger, args, stream, dict): where debugger is an object wrapping an LLDB SBDebugger args is the command line arguments, as an unparsed Python string stream is an SBStream that represents the standard output dict is an internal utility parameter and should be left untouched The function should return None on no error, or an error string to describe any problems llvm-svn: 137722
* Update the SBAddress.i Python interface file to the latest SBAddress.h,Johnny Chen2011-08-121-0/+40
| | | | | | and add some docstrings. llvm-svn: 137528
* Fixed an issue where LLDB was complaining about the lack of 'update' in a ↵Enrico Granata2011-08-111-0/+15
| | | | | | synthetic provider, despite it being optional llvm-svn: 137330
* Add logic to SBValue.linked_list_iter() to detect infinite loop and to bail ↵Johnny Chen2011-08-111-1/+5
| | | | | | | | | | | | out early. Add code to test case to create an evil linked list with: task_evil -> task_2 -> task_3 -> task_evil ... and to check that the linked list iterator only iterates 3 times. llvm-svn: 137291
* Change the SBValue.linked_list_iter() to treat the value object as a ↵Johnny Chen2011-08-111-2/+4
| | | | | | | | | | | | | homogeneous linked list data structure where an empty linked list is represented as a value object with a NULL value, instead of a special value object which 'points' to NULL. Also modifies the test case to comply. rdar://problem/9933692 llvm-svn: 137289
* On second thought, add the IsValid() method to SBTypeList, making it similar ↵Johnny Chen2011-08-051-0/+3
| | | | | | | | to SBSymbolContextList and SBValueList. Modify the test suite accordingly. llvm-svn: 136990
* Add SBType.GetBasicType() to the test scenario.Johnny Chen2011-08-051-0/+73
| | | | | | Add docstring for SBType, too. llvm-svn: 136983
* Add docstring & example usage for SBTypeList.Johnny Chen2011-08-051-0/+31
| | | | llvm-svn: 136979
* Fix indentation and remove the private section of SBTypeList.Johnny Chen2011-08-051-58/+54
| | | | | | SWIG doesn't care about the private section of class SBTypeList. llvm-svn: 136976
* o modify-python-lldb.py:Johnny Chen2011-08-051-2/+3
| | | | | | | | | | | | | | | Add the rich comparison methods (__eq__, __ne__) to SBType, too. o lldbtest.py: Add debug utility method TestBase.DebugSBType(). o test/python_api/type: Add tests for exercising SBType/SBTypeList API, including the SBTarget.FindTypes(type_name) API which returns a SBTypeList matching the type_name. llvm-svn: 136975
* The recently introduced SBTypeList is also iterable.Johnny Chen2011-08-051-2/+3
| | | | | | | This patch takes some time because the old Python constructor pattern was not a valid one, and breaks with SBTypeList's __init__ signature. Oops. llvm-svn: 136958
* APIs to GetValueAsSigned/Unsigned() in SBValue now also accept an SBError ↵Enrico Granata2011-08-041-1/+7
| | | | | | | | | parameter to give more info about any problem The synthetic children providers now use the new (safer) APIs to get the values of objects As a side effect, fixed an issue in ValueObject where ResolveValue() was not always updating the value before reading it llvm-svn: 136861
* Cleaned up the SBType.h file to not include internal headers and reorganizedGreg Clayton2011-08-032-33/+7
| | | | | | | | | | | | | | | | | | the SBType implementation classes. Fixed LLDB core and the test suite to not use deprecated SBValue APIs. Added a few new APIs to SBValue: int64_t SBValue::GetValueAsSigned(int64_t fail_value=0); uint64_t SBValue::GetValueAsUnsigned(uint64_t fail_value=0) llvm-svn: 136829
* Public API changes:Enrico Granata2011-07-294-86/+100
| | | | | | | | | | | | | | | | | | | | | - Completely new implementation of SBType - Various enhancements in several other classes Python synthetic children providers for std::vector<T>, std::list<T> and std::map<K,V>: - these return the actual elements into the container as the children of the container - basic template name parsing that works (hopefully) on both Clang and GCC - find them in examples/synthetic and in the test suite in functionalities/data-formatter/data-formatter-python-synth New summary string token ${svar : - the syntax is just the same as in ${var but this new token lets you read the values coming from the synthetic children provider instead of the actual children - Python providers above provide a synthetic child len that returns the number of elements into the container Full bug fix for the issue in which getting byte size for a non-complete type would crash LLDB Several other fixes, including: - inverted the order of arguments in the ClangASTType constructor - EvaluationPoint now only returns SharedPointer's to Target and Process - the help text for several type subcommands now correctly indicates argument-less options as such llvm-svn: 136504
* The SBValue.linked_list_iter() API failed for an empty list.Johnny Chen2011-07-271-3/+1
| | | | | | Fix the bug and add a test case. llvm-svn: 136265
* Add docstrings and cross refs to SBCompileUnit and SBLineEntry.Johnny Chen2011-07-272-3/+33
| | | | llvm-svn: 136230
* Add cross reference to SBThread from the SBFrame docstring. Also add a ↵Johnny Chen2011-07-271-1/+7
| | | | | | simple iteration example. llvm-svn: 136227
* Add deprecation docstrings for some APIs which take an SBFrame - SBValues ↵Johnny Chen2011-07-271-7/+18
| | | | | | know their own frames. llvm-svn: 136194
* Fix indentation and add a docstring for the ctor.Johnny Chen2011-07-261-4/+6
| | | | llvm-svn: 136187
* adding required utility function to SWIG interfaceEnrico Granata2011-07-261-0/+43
| | | | llvm-svn: 136147
* We can do better with the SBValue.linked_list_iter() API by supplying a defaultJohnny Chen2011-07-261-12/+16
| | | | | | | | | | | | | | end of list test function as __eol_test__. The simple example can be reduced to: for t in task_head.linked_list_iter('next'): print t Modify the test program to exercise the API for both cases: supplying or not supplying an end of list test function. llvm-svn: 136144
* The test function to determine whether we have reached the end of the list wasJohnny Chen2011-07-261-14/+7
| | | | | | | | | | | too complex in the test case. We can just simply test that the SBValue object is a valid object and it does not correspond to a null pointer in order to say that EOL has not been reached. Modify the test case and the lldb.py docstring to have a more compact test function. llvm-svn: 136123
* lldb.swig (the SWIG input file) has become too large. Modularize a bit by ↵Johnny Chen2011-07-262-0/+637
| | | | | | | | introducing two files to be included from lldb.swig: python-typemaps.swig and python-wrapper.swig. llvm-svn: 136117
* Rename the parameter for the end-of-list test function from end_of_list to ↵Johnny Chen2011-07-251-2/+2
| | | | | | end_of_list_test. llvm-svn: 136016
* Add cross references between the docstrings for regular SBValue iteration:Johnny Chen2011-07-252-6/+16
| | | | | | | | | | | | for child in value: # do something with the child value and SBValue.linked_list_iter(): for task in task_head.linked_list_iter('next', eol_test): # visit each item in the linked list llvm-svn: 136015
* Provide an add-on API to SBValue class by post-processing to provide a wayJohnny Chen2011-07-251-0/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to iterate through an SBValue instance by treating it as the head of a linked list. API program must provide two args to the linked_list_iter() method: the first being the child member name which points to the next item on the list and the second being a Python function which an SBValue (for the next item) and returns True if end of list is reached, otherwise it returns False. For example, suppose we have the following sample program. #include <stdio.h> class Task { public: int id; Task *next; Task(int i, Task *n): id(i), next(n) {} }; int main (int argc, char const *argv[]) { Task *task_head = new Task(-1, NULL); Task *task1 = new Task(1, NULL); Task *task2 = new Task(2, NULL); Task *task3 = new Task(3, NULL); // Orphaned. Task *task4 = new Task(4, NULL); Task *task5 = new Task(5, NULL); task_head->next = task1; task1->next = task2; task2->next = task4; task4->next = task5; int total = 0; // Break at this line Task *t = task_head; while (t != NULL) { if (t->id >= 0) ++total; t = t->next; } printf("We have a total number of %d tasks\n", total); return 0; } The test program produces the following output while exercising the linked_list_iter() SBVAlue API: task_head: TypeName -> Task * ByteSize -> 8 NumChildren -> 2 Value -> 0x0000000106400380 ValueType -> local_variable Summary -> None IsPointerType -> True Location -> 0x00007fff65f06e60 (Task *) next = 0x0000000106400390 (int) id = 1 (Task *) next = 0x00000001064003a0 (Task *) next = 0x00000001064003a0 (int) id = 2 (Task *) next = 0x00000001064003c0 (Task *) next = 0x00000001064003c0 (int) id = 4 (Task *) next = 0x00000001064003d0 (Task *) next = 0x00000001064003d0 (int) id = 5 (Task *) next = 0x0000000000000000 llvm-svn: 135938
* Make the SBAddress class easier to use when using the publicGreg Clayton2011-07-222-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | API. SBTarget changes include changing: bool SBTarget::ResolveLoadAddress (lldb::addr_t vm_addr, lldb::SBAddress& addr); to be: lldb::SBAddress SBTarget::ResolveLoadAddress (lldb::addr_t vm_addr); SBAddress can how contruct itself using a load address and a target which can be used to resolve the address: SBAddress (lldb::addr_t load_addr, lldb::SBTarget &target); This will actually just call the new SetLoadAddress accessor: void SetLoadAddress (lldb::addr_t load_addr, lldb::SBTarget &target); This function will always succeed in making a SBAddress object that can be used in API calls (even if "target" isn't valid). If "target" is valid and there are sections currently loaded, then it will resolve the address to a section offset address if it can. Else an address with a NULL section and an offset that is the "load_addr" that was passed in. We do this because a load address might be from the heap or stack. llvm-svn: 135770
* Change docstring wording: from 'method' to 'function'.Johnny Chen2011-07-211-1/+1
| | | | llvm-svn: 135648
* Add docstring for SBInstructionList class.Johnny Chen2011-07-211-0/+14
| | | | llvm-svn: 135647
* Add docstring for SBCommandReturnObject class.Johnny Chen2011-07-211-0/+7
| | | | llvm-svn: 135642
* Add docstring for SBCommandInterpreter class.Johnny Chen2011-07-201-0/+44
| | | | llvm-svn: 135631
* Add docstring for SBBroadcaster class.Johnny Chen2011-07-201-0/+11
| | | | llvm-svn: 135630
* Add some docstrings for SBFileSpec class.Johnny Chen2011-07-201-0/+21
| | | | llvm-svn: 135553
* Add some docstrings for SBError class.Johnny Chen2011-07-201-0/+47
| | | | llvm-svn: 135547
OpenPOWER on IntegriCloud