Skip to content
  1. Sep 12, 2012
  2. Sep 11, 2012
  3. Sep 10, 2012
  4. Sep 08, 2012
  5. Sep 07, 2012
    • Greg Clayton's avatar
      ba1fad84
    • Greg Clayton's avatar
      Train LLDB to deal with bad linker N_SO entries that point to our source files... · 0662d966
      Greg Clayton authored
      Train LLDB to deal with bad linker N_SO entries that point to our source files for debug map + DWARF in .o file debugging.
      
      llvm-svn: 163417
      0662d966
    • Greg Clayton's avatar
      Patch from Andrew Kaylor for linux: · e2186ed6
      Greg Clayton authored
      The attached patch fixes a problem with performing an attach from the SBTarget API on Linux (and other systems that use ProcessPOSIX).
       
      When Process::Attach was called from SBTarget, it resulted in a call to a form of the DoAttachWithID function that wasn't implemented in ProcessPOSIX, and so it fell back to the default implementation (which just returns an error).  It didn't seem necessary to use the attach_info parameter for this case, so I just implemented it as a call to the simpler version of the function.
       
      In debugging this problem, I also found that SBTarget wasn't checking the return value from the Attach call, causing it to hang when the attach fails.
      
      llvm-svn: 163399
      e2186ed6
    • Greg Clayton's avatar
      Patch from Andrew Kaylor for linux: · 542e4075
      Greg Clayton authored
      
      The attached patch adds support for debugging 32-bit processes when running a 64-bit lldb on an x86_64 Linux system.
       
      Making this work required two basic changes:
       
      1)      Getting lldb to report that it could debug 32-bit processes
      2)      Changing an assumption about how ptrace works when debugging cross-platform
       
      For the first change, I took a conservative approach and only enabled this for x86_64 Linux platforms.  It may be that the change I made in Host.cpp could be extended to other 64-bit Linux platforms, but I'm not familiar enough with the other platforms to know for sure.
       
      For the second change, the Linux ProcessMonitor class was assuming that ptrace(PTRACE_[PEEK|POKE]DATA...) would read/write a "word" based on the child process word size.  However, the ptrace documentation says that the "word" size read or written is "determined by the OS variant."  I verified experimentally that when ptracing a 32-bit child from a 64-bit parent a 64-bit word is read or written.
      
      llvm-svn: 163398
      542e4075
    • Jim Ingham's avatar
      f02a2e96
    • Jim Ingham's avatar
Loading