llvm-svn: 115537

the stdc++ library module.  Right now, it doesn't do any disassembly at all.  It
merely locates the stdc++ library.  Also tests the SBProcess object description
and verifies it is in a 'Stopped' state.

llvm-svn: 115536

llvm-svn: 115535

When a type comes from a previously-loaded PCH/AST file, don't try to write it into a chained PCH file.

llvm-svn: 115527

llvm-svn: 115526

llvm-svn: 115525

llvm-svn: 115524

section kind. Previously, optimized nops were only used for MachO.
Also added tests for ELF and COFF.

llvm-svn: 115523

Fixed and issue where we weren't seeing inlined functions anymore. We also now show the correct pc-offset within the inlined function. 

llvm-svn: 115522

already knows its own length, so this is redundant.

llvm-svn: 115521

llvm-svn: 115520

llvm-svn: 115519

llvm-svn: 115518

the {function.name}, is sufficient for this test case.

Plus added @expectedfailure decorator for a filed bug.

llvm-svn: 115517

llvm-svn: 115516

llvm-svn: 115515

${module.file.basename}{`${function.name}, is sufficient for this test case.

llvm-svn: 115514

Remove file:lineno from the expected substrings.

llvm-svn: 115512

llvm-svn: 115510

llvm-svn: 115509

using Clang in one way or another. Additions welcome!

llvm-svn: 115508

llvm-svn: 115506

llvm-svn: 115503

Removed the older style (in-allocator) problem construction system from the PBQP allocator. Problem construction is now done exclusively with the new builders.

llvm-svn: 115502

Ada in llvm-gcc.

llvm-svn: 115501

llvm-svn: 115500

llvm-svn: 115499

llvm-svn: 115498

llvm-svn: 115495

llvm-svn: 115494

llvm-svn: 115493

llvm-svn: 115491

was stopped in a module, yet had no valid function for the PC, no module would
be displayed.

llvm-svn: 115490

llvm-svn: 115489

llvm-svn: 115488

This has been applied already in r115093 on release_28.

llvm-svn: 115487

llvm-svn: 115486

instance:

settings set frame-format <string>
settings set thread-format <string>

This allows users to control the information that is seen when dumping
threads and frames. The default values are set such that they do what they
used to do prior to changing over the the user defined formats.

This allows users with terminals that can display color to make different
items different colors using the escape control codes. A few alias examples
that will colorize your thread and frame prompts are:

settings set frame-format 'frame #${frame.index}: \033[0;33m${frame.pc}\033[0m{ \033[1;4;36m${module.file.basename}\033[0;36m ${function.name}{${function.pc-offset}}\033[0m}{ \033[0;35mat \033[1;35m${line.file.basename}:${line.number}}\033[0m\n'

settings set thread-format 'thread #${thread.index}: \033[1;33mtid\033[0;33m = ${thread.id}\033[0m{, \033[0;33m${frame.pc}\033[0m}{ \033[1;4;36m${module.file.basename}\033[0;36m ${function.name}{${function.pc-offset}}\033[0m}{, \033[1;35mstop reason\033[0;35m = ${thread.stop-reason}\033[0m}{, \033[1;36mname = \033[0;36m${thread.name}\033[0m}{, \033[1;32mqueue = \033[0;32m${thread.queue}}\033[0m\n'

A quick web search for "colorize terminal output" should allow you to see what
you can do to make your output look like you want it.

The "settings set" commands above can of course be added to your ~/.lldbinit
file for permanent use.

Changed the pure virtual 
    void ExecutionContextScope::Calculate (ExecutionContext&);
To:
    void ExecutionContextScope::CalculateExecutionContext (ExecutionContext&);
    
I did this because this is a class that anything in the execution context
heirarchy inherits from and "target->Calculate (exe_ctx)" didn't always tell
you what it was really trying to do unless you look at the parameter.

llvm-svn: 115485

llvm-svn: 115484

llvm-svn: 115483