multiple checks are exposed as separate checkers, but CheckerManager only creates
one Checker object.

llvm-svn: 148525

llvm-svn: 148524

to find data on the heap. To use this, make the project and then when stopped in your
lldb debug session:

(lldb) process load /path/to/libheap.dylib
(lldb) find_pointer_in_heap (0x112233000000)

This will grep everything in all active allocation blocks and print and malloc blocks that contain the pointer 0x112233000000.

This can also work for c strings:

(lldb) find_cstring_in_heap ("hello")

llvm-svn: 148523

Remove PotentiallyPotentiallyEvaluated, and replace it with a much simpler and less error-prone way of handling the relevant cases.  Towards marking of whether a declaration is used more accurately.

llvm-svn: 148522

Add comment describing the interaction of WantsRawCommandString()/WantsCompletion() with the completion mechanism.

llvm-svn: 148521

'insertvalue' instructions that recreate the structure returned by the
'landingpad' instruction. Because the 'insertvalue' instruction isn't supported
by FastISel, this can save a bit of time during -O0 compilation.

llvm-svn: 148520

llvm-svn: 148518

printing.

llvm-svn: 148517

at the given location. 

This could be useful when checkers' logic depends on whether a function
is called with a given macro argument.

llvm-svn: 148516

This solves a the issue of crashing gdb when dumping a symbol; +
consistent vitualization.

llvm-svn: 148515

llvm-svn: 148514

llvm-svn: 148513

We should ultimately introduce GetAs...Type
functions in all cases where we have Is...Type
functions that know how to look inside typedefs.

llvm-svn: 148512

Enable full functionality of shared_ptr<const void> by adding allocator<const void>.  Credit to John Hurley for discovering this bug.

llvm-svn: 148508

a memory leak.

llvm-svn: 148507

template definitions.

llvm-svn: 148506

constexpr.

llvm-svn: 148505

http://llvm.org/viewvc/llvm-project?rev=148491&view=rev check in broke the argument completion
for "settings set th", followed by TAB.  Provide a way for commands who want raw commands to
hook into the completion mechanism.

llvm-svn: 148500

!=, %=, ^=, &=, *=, -=, |=, /=, <<=, <=, >=, and >>= to =.

llvm-svn: 148499

llvm-svn: 148497

llvm-svn: 148496

llvm-svn: 148495

<rdar://problem/10719481>

llvm-svn: 148494

llvm-svn: 148493

Add a new form of MCOperand, for representing sub-instructions.  This is intended for supporting bundles through the MC layer, rather than lowering them pre-MC as we currently do for Thumb2 IT blocks.  Since these sub-instruction operands hold pointers to the sub-instructions, it is the responsibility of the target's AsmPrinter to provide storage for them for the duration of the EmitInstruction() call.

llvm-svn: 148492

Fixed an issue where backtick char is not properly honored when setting the frame-format variable, like the following:

(lldb) settings set frame-format frame #${frame.index}: ${frame.pc}{ ${module.file.basename}{`${function.name-with-args}${function.pc-offset}}}{ at ${line.file.basename}:${line.number}}\n
(lldb) settings show frame-format
frame-format (string) = "frame #${frame.index}: ${frame.pc}{ `${module.file.basename}{${function.name-with-args}${function.pc-offset}}}{` at ${line.file.basename}:${line.number}}\n"
(lldb)

o CommandObjectSettings.h/.cpp:

  Modify the command object impl to require raw command string instead of parsed command string,
  which also fixes an outstanding issue that customizing the prompt with trailing spaces doesn't
  work.

o Args.cpp:

  During CommandInterpreter::HandleCommand(), there is a PreprocessCommand phase which already
  strips/processes pairs of backticks as an expression eval step.  There's no need to treat
  a backtick as starting a quote.

o TestAbbreviations.py and change_prompt.lldb:

  Fixed incorrect test case/logic.

o TestSettings.py:

  Remove expectedFailure decorator.

llvm-svn: 148491

rdar://10531041.

llvm-svn: 148490

llvm-svn: 148489

originally imported from symbols for the expression
parser didn't get their superclasses set properly.

llvm-svn: 148488

llvm-svn: 148487

llvm-svn: 148486

llvm-svn: 148485

that the given source range encompasses.

llvm-svn: 148481

and returns a character range with file locations.

llvm-svn: 148480

start/end location.

It is commonly needed after calling the function; with this way we avoid
recalculating it.

llvm-svn: 148479

llvm-svn: 148478

By scanning the thread list backwards.

llvm-svn: 148476

llvm-svn: 148475

llvm-svn: 148474

llvm-svn: 148473