Enrico Granata e9a09c74fa Add an API on SBValueList to find the first value with a given name stored in the list ...

llvm-svn: 222576

2014-11-21 21:45:03 +00:00

..

SBAddress.i

…

SBBlock.i

…

SBBreakpoint.i

…

SBBreakpointLocation.i

…

SBBroadcaster.i

…

SBCommandInterpreter.i

…

SBCommandReturnObject.i

…

SBCommunication.i

…

SBCompileUnit.i

…

SBData.i

…

SBDebugger.i

…

SBDeclaration.i

…

SBError.i

…

SBEvent.i

…

SBExecutionContext.i

…

SBExpressionOptions.i

…

SBFileSpec.i

…

SBFileSpecList.i

…

SBFrame.i

…

SBFunction.i

…

SBHostOS.i

…

SBInstruction.i

…

SBInstructionList.i

…

SBLineEntry.i

…

SBListener.i

…

SBModule.i

…

SBModuleSpec.i

…

SBPlatform.i

…

SBProcess.i

…

SBQueue.i

…

SBQueueItem.i

…

SBSection.i

…

SBSourceManager.i

…

SBStream.i

…

SBStringList.i

…

SBSymbol.i

…

SBSymbolContext.i

…

SBSymbolContextList.i

…

SBTarget.i

Add documentation for the SBTarget::ReadInstructions and

2014-11-18 05:43:11 +00:00

SBThread.i

…

SBThreadCollection.i

…

SBThreadPlan.i

…

SBType.i

…

SBTypeCategory.i

…

SBTypeEnumMember.i

…

SBTypeFilter.i

…

SBTypeFormat.i

…

SBTypeNameSpecifier.i

…

SBTypeSummary.i

…

SBTypeSynthetic.i

…

SBUnixSignals.i

…

SBValue.i

Shuffle APIs around a little bit, so that if you pass custom summary 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

2014-11-18 23:36:25 +00:00

SBValueList.i

Add an API on SBValueList to find the first value with a given name stored in the list

2014-11-21 21:45:03 +00:00

SBWatchpoint.i

…