llvm-svn: 126531

the intermediate files built with the same dictionary during test execution.

llvm-svn: 126530

current working directory when running the inferior.  Radar filed:

    # rdar://problem/9056462
    # The process launch flag '-w' for setting the current working directory not working?

llvm-svn: 126529

llvm-svn: 126517

llvm-svn: 126516

llvm-svn: 126515

related to 'process launch' command.

llvm-svn: 126514

of Stephen Wilson's idea (thanks for the input Stephen!). What I ended up
doing was:
- Got rid of ArchSpec::CPU (which was a generic CPU enumeration that mimics
  the contents of llvm::Triple::ArchType). We now rely upon the llvm::Triple 
  to give us the machine type from llvm::Triple::ArchType.
- There is a new ArchSpec::Core definition which further qualifies the CPU
  core we are dealing with into a single enumeration. If you need support for
  a new Core and want to debug it in LLDB, it must be added to this list. In
  the future we can allow for dynamic core registration, but for now it is
  hard coded.
- The ArchSpec can now be initialized with a llvm::Triple or with a C string
  that represents the triple (it can just be an arch still like "i386").
- The ArchSpec can still initialize itself with a architecture type -- mach-o
  with cpu type and subtype, or ELF with e_machine + e_flags -- and this will
  then get translated into the internal llvm::Triple::ArchSpec + ArchSpec::Core.
  The mach-o cpu type and subtype can be accessed using the getter functions:
  
  uint32_t
  ArchSpec::GetMachOCPUType () const;

  uint32_t
  ArchSpec::GetMachOCPUSubType () const;
  
  But these functions are just converting out internal llvm::Triple::ArchSpec 
  + ArchSpec::Core back into mach-o. Same goes for ELF.

All code has been updated to deal with the changes.

This should abstract us until later when the llvm::TargetSpec stuff gets
finalized and we can then adopt it.

llvm-svn: 126278

llvm-svn: 126260

llvm-svn: 126257

a Stream, and then added GetOutputData & GetErrorData to get the accumulated data.
- Added a StreamTee that will tee output to two provided lldb::StreamSP's.
- Made the CommandObjectReturn use this so you can Tee the results immediately to
the debuggers output file, as well as saving up the results to return when the command
is done executing.
- HandleCommands now uses this so that if you have a set of commands that continue the target
you will see the commands come out as they are processed.
- The Driver now uses this to output the command results as you go, which makes the interface
more reactive seeming.

llvm-svn: 126015

llvm-svn: 125682

different build configurations.

llvm-svn: 125584

llvm-svn: 125522

checks that the process is stopped due to breakpoint at the specified line no.

llvm-svn: 125400

llvm-svn: 125323

llvm-svn: 125322

and constant strings.

llvm-svn: 125320

- Objective-C constant strings were being
  NULL-terminated erroneously.

- Empty Objective-C constant strings were not
  being generated correctly.

Also added the template for a test of these
fixes.

llvm-svn: 125314

llvm-svn: 125199

llvm-svn: 125100

llvm-svn: 125099

Modify test cases in test suite to either expect brief output or to pass -f for full
output as appropriate.

llvm-svn: 124905

    apropos 'environment variable'

searches all settings description and returns a topic related to:

    target.process.env-vars

llvm-svn: 124841

llvm-svn: 124828

llvm-svn: 124806

llvm-svn: 124764

llvm-svn: 124763

substitutions in order to achieve file mappings.

Modify CommandObjectTarget.cpp to properly set the status of the return object to make
scripting like this:

    self.runCmd("target image-search-paths add %s %s" % (os.getcwd(), new_dir))

works.

llvm-svn: 124762

more test cases

Fixed minor bug in the breakpoint id range translation code.

llvm-svn: 124729

it passes when using clang as the compiler to build the inferior.

llvm-svn: 124707

C++ virtual function and virtual inheritance.

llvm-svn: 124642

that you run into with inheritance.

llvm-svn: 124619

llvm-svn: 124600

llvm-svn: 124598

llvm-svn: 124594

llvm-svn: 124589

llvm-svn: 124517

to be used for the test run.  Could be useful for debugging the setup of the
test environment.

llvm-svn: 124516

llvm-svn: 124513