Skip to content
  1. Nov 21, 2011
  2. May 13, 2011
    • Johnny Chen's avatar
      This patch add a "fake" attach waiting for a real implementation and · 13e8e1c3
      Johnny Chen authored
      solve the build break due to the lack of this method.
      
      It also propose a solution to the API changes in RegisterContext.
      
      I upgraded also the the python version in the makefile. My linux
      installation has python2.7 and AFAIK also the latest ubuntu
      has this version of python so maybe is worth upgrading.
      
      Patch by Marco Minutoli <mminutoli@gmail.com>
      
      [Note: I had to hand merge in the diffs since patch thinks it is a corrupt patch.]
      
      llvm-svn: 131313
      13e8e1c3
  3. Apr 07, 2011
    • Stephen Wilson's avatar
      linux: remove ProcessLinux::FindProcesses · 0682ba2f
      Stephen Wilson authored
      This method only needs to be overridden in the remote debugging case,  the
      base class handles the host case.  Since we do not do remote debugging on
      Linux yet and there is a typo that causes a build issue, just remove this
      method for now.
       
      
      llvm-svn: 129069
      0682ba2f
  4. Apr 06, 2011
  5. Mar 26, 2011
  6. Mar 23, 2011
  7. Mar 08, 2011
    • Greg Clayton's avatar
      LLDB now has "Platform" plug-ins. Platform plug-ins are plug-ins that provide · e996fd30
      Greg Clayton authored
      an interface to a local or remote debugging platform. By default each host OS
      that supports LLDB should be registering a "default" platform that will be
      used unless a new platform is selected. Platforms are responsible for things
      such as:
      - getting process information by name or by processs ID
      - finding platform files. This is useful for remote debugging where there is 
        an SDK with files that might already or need to be cached for debug access.
      - getting a list of platform supported architectures in the exact order they
        should be selected. This helps the native x86 platform on MacOSX select the
        correct x86_64/i386 slice from universal binaries.
      - Connect to remote platforms for remote debugging
      - Resolving an executable including finding an executable inside platform
        specific bundles (macosx uses .app bundles that contain files) and also
        selecting the appropriate slice of universal files for a given platform.
      
      So by default there is always a local platform, but remote platforms can be
      connected to. I will soon be adding a new "platform" command that will support
      the following commands:
      (lldb) platform connect --name machine1 macosx connect://host:port
      Connected to "machine1" platform.
      (lldb) platform disconnect macosx
      
      This allows LLDB to be well setup to do remote debugging and also once 
      connected process listing and finding for things like:
      (lldb) process attach --name x<TAB>
      
      The currently selected platform plug-in can now auto complete any available
      processes that start with "x". The responsibilities for the platform plug-in
      will soon grow and expand.
      
      llvm-svn: 127286
      e996fd30
Loading