aboutsummaryrefslogtreecommitdiff
path: root/lldb/scripts/Python/interface
AgeCommit message (Collapse)AuthorFilesLines
2015-04-24Start to share SWIG interface files between languages.Bruce Mitchener57-9737/+0
Summary: Move scripts/Python/interface to scripts/interface so that we can start making iterative improvements towards sharing the interface files between multiple languages (each of which would have their own directory as now). Test Plan: Build and see. Reviewers: zturner, emaste, clayborg Reviewed By: clayborg Subscribers: mjsabby, lldb-commits Differential Revision: http://reviews.llvm.org/D9212 llvm-svn: 235676
2015-04-23Factor resolution of abbreviations and aliases so that they can be tested ↵Adrian McCarthy1-0/+3
directly. http://reviews.llvm.org/D9033 llvm-svn: 235633
2015-04-21Add properties to SBExecutionContext to access the several entities it ↵Enrico Granata1-0/+15
stores in a more Pythonic fashion llvm-svn: 235447
2015-03-23Turn off 'quit' confirmation in lldb-miIlia K1-0/+6
Summary: # Turn off interpreter.prompt-on-quit on startup (MI) # Add CommandInterpreter::SetPromptOnQuit # Add SBCommandInterpreter::GetPromptOnQuit/SetPromptOnQuit All tests pass on OS X. Test Plan: ``` -file-exec-and-symbols ~/p/hello -break-insert -f main -exec-run -interpreter-exec console quit ``` Reviewers: abidh, clayborg Reviewed By: abidh, clayborg Subscribers: lldb-commits, clayborg, abidh Differential Revision: http://reviews.llvm.org/D8444 llvm-svn: 233034
2015-03-23Fix missing interfaces to scripts/Python/interface after r229110, r231858 ↵Ilia K3-1/+28
and r232891 This includes: # SBCommandInterpreter::EventIsCommandInterpreterEvent # SBModule::GetSymbolFileSpec/GetObjectFileHeaderAddress # SBTarget::EventIsTargetEvent/GetTargetFromEvent/GetNumModulesFromEvent/GetModuleAtIndexFromEvent/GetLaunchInfo/SetLaunchInfo llvm-svn: 233029
2015-02-26[swig] Generate bindings for SBDebugger::*UseColor().Bruce Mitchener1-0/+6
Summary: These functions were added in 2013, but not added to the SWIG bindings. Reviewers: ki.stfu, clayborg Reviewed By: ki.stfu, clayborg Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D7909 llvm-svn: 230646
2015-02-20Rename the "glob arguments" feature to "shell expand arguments"Enrico Granata1-2/+2
This should not bring any feature change, except changing names of things here and there llvm-svn: 230077
2015-02-17Revert "Revert "I had recently added a new SBFrame::GetVariables() overload ↵Zachary Turner2-6/+62
with yet another bool argument"" Reverting this commit led to other failures which I did not see at first. This turned out to be an easy problem to fix, so I added SBVariablesOptions.cpp to the CMakeLists.txt. In the future please try to make sure new files are added to CMake. llvm-svn: 229516
2015-02-17Revert "I had recently added a new SBFrame::GetVariables() overload with yet ↵Zachary Turner2-62/+6
another bool argument" This reverts commit r228975. It was causing link errors on the Windows bots, since last Thursday. http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/725 Conflicts: lldb.xcodeproj/project.pbxproj llvm-svn: 229514
2015-02-16Extract SBAttachInfo into own set of files - SBAttachInfo.h, ↵Oleksiy Vyalov2-99/+111
SBAttachInfo.cpp and SBAttachInfo.i. llvm-svn: 229346
2015-02-12I had recently added a new SBFrame::GetVariables() overload with yet another ↵Enrico Granata2-6/+62
bool argument We talked about it internally - and came to the conclusion that it's time to have an options class This commit adds an SBVariablesOptions class and goes through all the required dance llvm-svn: 228975
2015-02-12Add an -A option to "break set -p" to search all files for matches. Also ↵Jim Ingham1-0/+3
add the version of SBTarget::BreakpointCreateBySourceRegex that takes file spec lists to the Python interface, and add a test for this. <rdar://problem/19805037> llvm-svn: 228938
2015-02-11Introduce the notion of "runtime support values"Enrico Granata2-0/+11
A runtime support value is a ValueObject whose only purpose is to support some language runtime's operation, but it does not directly provide any user-visible benefit As such, unless the user is working on the runtime support, it is mostly safe for them not to see such a value when debugging It is a language runtime's job to check whether a ValueObject is a support value, and that - in conjunction with a target setting - is used by frame variable and target variable SBFrame::GetVariables gets a new overload with yet another flag to dictate whether to return those support values to the caller - that which defaults to the setting's value rdar://problem/15539930 llvm-svn: 228791
2015-02-10And make the globbing behavior available via the SB APIEnrico Granata1-0/+6
llvm-svn: 228660
2015-02-04Extend SBPlatform with capability to launch/terminate a process remotely. ↵Oleksiy Vyalov3-111/+132
Integrate this change into test framework in order to spawn processes on a remote target. http://reviews.llvm.org/D7263 llvm-svn: 228230
2015-01-28Add logic to ClangASTType and SBType to discover information about vector typesEnrico Granata1-0/+6
llvm-svn: 227383
2014-12-17Provide CreateValueFromData,Expression at the SBTarget level as well as the ↵Enrico Granata1-0/+6
SBValue level; and also make all the implenentations agree on using the matching ValueObject::Create instead of doing code copypastas llvm-svn: 224460
2014-12-16Add the ability to tag one or more breakpoints with a name. TheseJim Ingham1-0/+12
names can then be used in place of breakpoint id's or breakpoint id ranges in all the commands that operate on breakpoints. <rdar://problem/10103959> llvm-svn: 224392
2014-12-15Provide a SBFrame.register/.reg helper on the Python side of SBFrame to vend ↵Enrico Granata1-0/+24
a flattened view of registers Our actual view of registers is a set of register sets, each one of which contains a subset of the actual registers This makes trivial scripting operations tedious ("I just want to read r7!") This helper allows things like: print lldb.frame.reg["r7"] Fixes rdar://19185662 llvm-svn: 224275
2014-12-08Add the ability for an SBValue to create a persisted version of itself.Enrico Granata1-0/+3
Such a persisted version is equivalent to evaluating the value via the expression evaluator, and holding on to the $n result of the expression, except this API can be used on SBValues that do not obviously come from an expression (e.g. are the result of a memory lookup) Expose this via SBValue::Persist() in our public API layer, and ValueObject::Persist() in the lldb_private layer Includes testcase Fixes rdar://19136664 llvm-svn: 223711
2014-11-22Fix mispelled 'ling' Python property to be 'line' inJason Molenda2-2/+2
SBLineEntry and SBDeclaration. Patch from Chris Willmore. <rdar://problem/19054323> llvm-svn: 222592
2014-11-21Per off-list feedback, this API returns the *first* value with a given name, ↵Enrico Granata1-1/+1
not the *only* one. Rename it to reflect that llvm-svn: 222582
2014-11-21Add an API on SBValueList to find the first value with a given name stored ↵Enrico Granata1-0/+4
in the list llvm-svn: 222576
2014-11-18Shuffle APIs around a little bit, so that if you pass custom summary ↵Enrico Granata1-1/+2
options, we don't end up caching the summary hence obtained. You may want to obtain an uncapped summary, but this should not be reflected in the summary we cache. The drawback is that we don't cache as aggressively as we could, but at least you get to have different summaries with different options without having to reset formatters or the SBValue at each step llvm-svn: 222280
2014-11-18Add documentation for the SBTarget::ReadInstructions andJason Molenda1-2/+27
SBTarget::GetInstructions APIs so it's a little clearer to understand which should be used. <rdar://problem/18787018> llvm-svn: 222225
2014-11-17Add APIs on SBFunction and SBCompileUnit to inquire about the language type ↵Enrico Granata2-0/+6
that the function/compile unit is defined in llvm-svn: 222189
2014-11-17Fixed more fallout from running the test suite remotely on iOS devices.Greg Clayton1-0/+12
Fixed include: - Change Platform::ResolveExecutable(...) to take a ModuleSpec instead of a FileSpec + ArchSpec to help resolve executables correctly when we have just a path + UUID (no arch). - Add the ability to set the listener in SBLaunchInfo and SBAttachInfo in case you don't want to use the debugger as the default listener. - Modified all places that use the SBLaunchInfo/SBAttachInfo and the internal ProcessLaunchInfo/ProcessAttachInfo to not take a listener as a parameter since it is in the launch/attach info now - Load a module's sections by default when removing a module from a target. Since we create JIT modules for expressions and helper functions, we could end up with stale data in the section load list if a module was removed from the target as the section load list would still have entries for the unloaded module. Target now has the following functions to help unload all sections a single or multiple modules: size_t Target::UnloadModuleSections (const ModuleList &module_list); size_t Target::UnloadModuleSections (const lldb::ModuleSP &module_sp); llvm-svn: 222167
2014-11-13Do not override the existing definition of addr_size when adding new ↵Enrico Granata1-2/+2
properties to SBTarget. Fixes rdar://18963842 llvm-svn: 221850
2014-11-06Introduce the notion of "type summary options" as flags that can be passed ↵Enrico Granata2-1/+28
down to individual summary formatters to alter their behavior in a formatter-dependent way Two flags are introduced: - preferred display language (as in, ObjC vs. C++) - summary capping (as in, should a limit be put to the amount of data retrieved) The meaning - if any - of these options is for individual formatters to establish The topic of a subsequent commit will be to actually wire these through to individual data formatters llvm-svn: 221482
2014-10-28Add a few functions to SBType to handle arrays and typedefs. Fixes ↵Enrico Granata1-0/+9
rdar://12675166 llvm-svn: 220824
2014-10-22Added functions to the C++ API, for the benefit of non-8-bit byte architectures.Matthew Gardiner2-0/+105
New functions to give client applications to tools to discover target byte sizes for addresses prior to ReadMemory. Also added GetPlatform and ReadMemory to the SBTarget class, since they seemed to be useful utilities to have. Each new API has had a test case added. http://reviews.llvm.org/D5867 llvm-svn: 220372
2014-10-21Expose the type-info flags at the public API layer. These flags provide much ↵Enrico Granata1-0/+3
more informational content to consumers of the LLDB API than the existing TypeClass. Part of the fix for rdar://18517593 llvm-svn: 220322
2014-10-14This adds a "batch mode" to lldb kinda like the gdb batch mode. It will ↵Jim Ingham2-1/+11
quit the debugger after all the commands have been executed except if one of the commands was an execution control command that stopped because of a signal or exception. Also adds a variant of SBCommandInterpreter::HandleCommand that takes an SBExecutionContext. That way you can run an lldb command targeted at a particular target, thread or process w/o having to select same before running the command. Also exposes CommandInterpreter::HandleCommandsFromFile to the SBCommandInterpreter API, since that seemed generally useful. llvm-svn: 219654
2014-10-11Add a IsInstrumentationRuntimePresent SB APIKuba Brecka1-0/+3
Reviewed at http://reviews.llvm.org/D5738 This adds an SB API into SBProcess: bool SBProcess::IsInstrumentationRuntimePresent(InstrumentationRuntimeType type); which simply tells whether a particular InstrumentationRuntime (read "ASan") plugin is present and active. llvm-svn: 219560
2014-10-11Rework the way we pass "run multiple command" options to the various API's thatJim Ingham2-3/+70
do that (RunCommandInterpreter, HandleCommands, HandleCommandsFromFile) to gather the options into an options class. Also expose that to the SB API's. Change the way the "-o" options to the lldb driver are processed so: 1) They are run synchronously - didn't really make any sense to run the asynchronously. 2) The stop on error 3) "quit" in one of the -o commands will not quit lldb - not the command interpreter that was running the -o commands. I added an entry to the run options to stop-on-crash, but I haven't implemented that yet. llvm-svn: 219553
2014-10-10LLDB AddressSanitizer instrumentation runtime plugin, breakpint on error and ↵Kuba Brecka1-0/+8
report data extraction Reviewed at http://reviews.llvm.org/D5592 This patch gives LLDB some ability to interact with AddressSanitizer runtime library, on top of what we already have (historical memory stack traces provided by ASan). Namely, that's the ability to stop on an error caught by ASan, and access the report information that are associated with it. The report information is also exposed into SB API. More precisely this patch... adds a new plugin type, InstrumentationRuntime, which should serve as a generic superclass for other instrumentation runtime libraries, these plugins get notified when modules are loaded, so they get a chance to "activate" when a specific dynamic library is loaded an instance of this plugin type, AddressSanitizerRuntime, which activates itself when it sees the ASan dynamic library or founds ASan statically linked in the executable adds a collection of these plugins into the Process class AddressSanitizerRuntime sets an internal breakpoint on __asan::AsanDie(), and when this breakpoint gets hit, it retrieves the report information from ASan this breakpoint is then exposed as a new StopReason, eStopReasonInstrumentation, with a new StopInfo subclass, InstrumentationRuntimeStopInfo the StopInfo superclass is extended with a m_extended_info field (it's a StructuredData::ObjectSP), that can hold arbitrary JSON-like data, which is the way the new plugin provides the report data the "thread info" command now accepts a "-s" flag that prints out the JSON data of a stop reason (same way the "-j" flag works now) SBThread has a new API, GetStopReasonExtendedInfoAsJSON, which dumps the JSON string into a SBStream adds a test case for all of this I plan to also get rid of the original ASan plugin (memory history stack traces) and use an instance of AddressSanitizerRuntime for that purpose. Kuba llvm-svn: 219546
2014-10-01Add a new SBExecutionContext class that wraps an ExecutionContextRef. This ↵Enrico Granata1-0/+42
class is a convenient way at the API level to package a target,process,thread and frame all together - or just a subset of those llvm-svn: 218808
2014-09-29This checkin is the first step in making the lldb thread stepping mechanism ↵Jim Ingham2-0/+126
more accessible from the user level. It adds the ability to invent new stepping modes implemented by python classes, and to view the current thread plan stack and to some extent alter it. I haven't gotten to documentation or tests yet. But this should not cause any behavior changes if you don't use it, so its safe to check it in now and work on it incrementally. llvm-svn: 218642
2014-09-19Fix for 218140 for SBTarget.i, the added functions were in the wrong class ↵Carlo Kok1-10/+11
definition llvm-svn: 218147
2014-09-19Adds two new functions to SBTarget FindGlobalVariables and ↵Carlo Kok1-0/+9
FindGlobalFunctions that lets you search by name, by regular expression and by starts with. llvm-svn: 218140
2014-09-19Extend the member function discovery APIs to also support Objective-C as ↵Enrico Granata1-0/+9
well as C++ For the Objective-C case, we do not have a "function type" notion, so we actually end up wrapping the clang ObjCMethodDecl in the Impl object, and ask function-y questions of it In general, you can always ask for return type, number of arguments, and type of each argument using the TypeMemberFunction layer - but in the C++ case, you can also acquire a Type object for the function itself, which instead you can't do in the Objective-C case llvm-svn: 218132
2014-09-15Change SBType.GetMemberFunctionAtIndex() to return an object describing the ↵Enrico Granata1-1/+30
member function in more detail. A type was really quite vague. This now has function name, kind, as well as function type llvm-svn: 217828
2014-09-12Add logic to LLDB to figure out the types of member functions of C++ ↵Enrico Granata1-0/+6
classes. Add plumbing for that all the way up to the SB layer llvm-svn: 217701
2014-09-06Implement ASan history threads in SB APIKuba Brecka1-0/+3
Reviewed at http://reviews.llvm.org/D5219 and http://lists.cs.uiuc.edu/pipermail/lldb-commits/Week-of-Mon-20140901/012809.html llvm-svn: 217300
2014-09-06Expose the ability to retrieve the result of a type validator via the SB ↵Enrico Granata1-0/+3
API. To keep it simple, do not expose the pair, but just return a NULL string for success, and a non-NULL string for error; If we were to decide to expose the pair, we would need an SBTypeValidatorResult, which is fine, but it should come as part of exposing type validators through the SB API rather than as a one-off thing. So, KISS for now llvm-svn: 217299
2014-09-06Expose ThreadCollection in SB APIKuba Brecka1-0/+38
Reviewed at http://reviews.llvm.org/D5218 and http://lists.cs.uiuc.edu/pipermail/lldb-commits/Week-of-Mon-20140901/012828.html llvm-svn: 217296
2014-08-27Make it clear that the load_addr property on SBAddress relies on lldb.target, Jim Ingham1-1/+1
and so can only be used in the script interpreter. llvm-svn: 216625
2014-08-11Fix some typos:Sylvestre Ledru1-1/+1
* transfered => transferred * unkown => unknown * sucessfully => successfully llvm-svn: 215367
2014-08-08Add an option to suppress the persistent result variable when running ↵Jim Ingham1-0/+9
EvaluateExpression from Python. If you don't need to refer to the result in another expression, there's no need to bloat the persistent variable table with them since you already have the result SBValue to work with. <rdar://problem/17963645> llvm-svn: 215244
2014-07-30(no commit message)Greg Clayton1-0/+6
llvm-svn: 214319
generated by cgit v1.1 at 2025-10-04 06:08:44 +0000