Skip to content
  1. Jun 01, 2011
  2. May 31, 2011
  3. May 30, 2011
  4. May 29, 2011
  5. May 28, 2011
  6. May 27, 2011
  7. May 26, 2011
  8. May 25, 2011
    • Johnny Chen's avatar
      Modified to use SBTarget.LaunchSimple() API. · 2cf62497
      Johnny Chen authored
      llvm-svn: 132082
      2cf62497
    • Johnny Chen's avatar
      Use built-in truth value testing. · 9a26f0f2
      Johnny Chen authored
      llvm-svn: 132079
      9a26f0f2
    • Johnny Chen's avatar
      Use built-in truth value testing. · 26fc16b0
      Johnny Chen authored
      llvm-svn: 132078
      26fc16b0
    • Johnny Chen's avatar
      3cd1e551
    • Greg Clayton's avatar
      Bumping Xcode project versions for lldb-55 and debugserver-139. · 60d4d9eb
      Greg Clayton authored
      llvm-svn: 132067
      60d4d9eb
    • Greg Clayton's avatar
      Added some comments. · 1cbc52cd
      Greg Clayton authored
      llvm-svn: 132066
      1cbc52cd
    • Greg Clayton's avatar
      ABI plug-ins must implement the following pure virtual functions: · 9b72eb71
      Greg Clayton authored
      virtual bool
      ABI::StackUsesFrames () = 0;
      
      Should return true if your ABI uses frames when doing stack backtraces. This
      means a frame pointer is used that points to the previous stack frame in some
      way or another.
      
      virtual bool
      ABI::CallFrameAddressIsValid (lldb::addr_t cfa) = 0;
      
      Should take a look at a call frame address (CFA) which is just the stack
      pointer value upon entry to a function. ABIs usually impose alignment
      restrictions (4, 8 or 16 byte aligned), and zero is usually not allowed.
      This function should return true if "cfa" is valid call frame address for
      the ABI, and false otherwise. This is used by the generic stack frame unwinding
      code to help determine when a stack ends.
      
      virtual bool
      ABI::CodeAddressIsValid (lldb::addr_t pc) = 0;    
      
      Validates a possible PC value and returns true if an opcode can be at "pc".
      Some ABIs or architectures have fixed width instructions and must be aligned
      to a 2 or 4 byte boundary. "pc" can be an opcode or a callable address which
      means the load address might be decorated with extra bits (such as bit zero
      to indicate a thumb function call for ARM targets), so take this into account
      when returning true or false. The address should also be validated to ensure
      it is a valid address for the address size of the inferior process. 32 bit
      targets should make sure the address is less than UINT32_MAX.
      
      Modified UnwindLLDB to use the new ABI functions to help it properly terminate
      stacks.
      
      
      Modified the mach-o function that extracts dependent files to not resolve the
      path as the paths inside a binary might not match those on the current
      host system.
      
      llvm-svn: 132021
      9b72eb71
    • Johnny Chen's avatar
      Added comment. · 624ddf2f
      Johnny Chen authored
      llvm-svn: 132019
      624ddf2f
    • Johnny Chen's avatar
      Comment change. · 2f1ee9a0
      Johnny Chen authored
      llvm-svn: 132018
      2f1ee9a0
    • Johnny Chen's avatar
      Fix a potential bug resulting from the wrong assumption that SWIG puts out the __init__ · 93e7b3a8
      Johnny Chen authored
      method definition before other method definitions.  Instead, do without it and process
      the class with IsValid() method definition in all possible states.
      
      llvm-svn: 132016
      93e7b3a8
  9. May 24, 2011
Loading