Skip to content
  1. Jul 09, 2013
    • Daniel Malea's avatar
      Add TestConcurrentEvents test for LLDB's handling of inferior threads · b3d41a27
      Daniel Malea authored
      - Test verifies LLDB's handling of inferiors with threads that: hit breakpoints,
        modfiy variables that have watchpoints set, generate user signals, and crash.
      - Add a few "stress tests" (with ~100 threads) -- run these with "-l" dotest.py
        flag.
      - Fix stop_reason_to_str helper in lldbutil to handle eStopReasonThreadExited.
      - Add sort_stopped_threads helper to lldbutil to separate thread lists based
        on stop reason.
      
      Logged llvm.org/pr16566 and llvm.org/pr16567 for bugs exposed.
      
      llvm-svn: 185889
      b3d41a27
    • Greg Clayton's avatar
      Added missing SBModuleSpec.cpp file to the CMakeLists.txt · 4670d47f
      Greg Clayton authored
      llvm-svn: 185878
      4670d47f
    • Greg Clayton's avatar
      Added a way to extract the module specifications from a file. A module... · 226cce25
      Greg Clayton authored
      Added a way to extract the module specifications from a file. A module specification is information that is required to describe a module (executable, shared library, object file, ect). This information includes host path, platform path (remote path), symbol file path, UUID, object name (for objects in .a files for example you could have an object name of "foo.o"), and target triple. Module specification can be used to create a module, or used to add a module to a target. A list of module specifications can be used to enumerate objects in container objects (like universal mach files and BSD archive files).
      
      There are two new classes:
      
      lldb::SBModuleSpec
      lldb::SBModuleSpecList
      
      The SBModuleSpec wraps up a lldb_private::ModuleSpec, and SBModuleSpecList wraps up a lldb_private::ModuleSpecList.
      
      llvm-svn: 185877
      226cce25
  2. Jul 08, 2013
  3. Jul 04, 2013
  4. Jul 03, 2013
  5. Jul 02, 2013
  6. Jul 01, 2013
  7. Jun 29, 2013
  8. Jun 28, 2013
    • Sean Callanan's avatar
      Hitherto the IRForTarget infrastructure has mainly · 1f9db3eb
      Sean Callanan authored
      been suitable for preparing a single IR function
      for operation in the target.  However, using blocks
      and lambdas creates other IR functions that also
      need to be processed.
      
      I have audited IRForTarget to make it process
      multiple functions.  Where IRForTarget would add
      new instructions at the beginning of the main
      expression function, it now adds them on-demand
      in the function where they are needed.  This is
      enabled by a system of FunctionValueCaches, which
      invoke a lambda to create or derive the values as
      needed, or report the result of that lambda if it
      has already been called for the given function.
      
      <rdar://problem/14180236>
      
      llvm-svn: 185224
      1f9db3eb
    • Greg Clayton's avatar
      Default parameters are evil and should not be used. Case and point this... · 0d551045
      Greg Clayton authored
      Default parameters are evil and should not be used. Case and point this checkin that fixes implicit conversions that were happening.
      
      llvm-svn: 185217
      0d551045
Loading