[lldb-dev] LLDB-MI remote debugging on Linux
Scott Funkenhauser via lldb-dev
lldb-dev at lists.llvm.org
Thu Apr 20 10:59:17 PDT 2017
What would be a reasonable solution?
Does having the lldb-server read the shared libraries from disk (instead of
from the process's memory) sound sensible?
On Thu, Apr 20, 2017 at 10:30 AM, Pavel Labath <labath at google.com> wrote:
> this is a known problem and somewhat embarrassing problem, but
> unfortunately we haven't had time to look at that yet. The code that is
> doing that was added to support loading of the vdso, which is only present
> in the application memory (and it is a full elf file). I don't think
> anybody has realized the full implications of this when it was being added.
> Patches fixing this would be very wellcome.
> On 19 April 2017 at 15:17, Scott Funkenhauser via lldb-dev <
> lldb-dev at lists.llvm.org> wrote:
>> I'm exploring using lldb-mi and lldb-server to remotely debug a process
>> running on a Linux host. I'm running into an issue where lldb-mi is
>> failing to load the ELF section headers from the remote process's memory
>> for certain shared libraries.
>> Looking at ObjectFileELF:GetSectionHeaderInfo I believe it is trying to
>> read the section headers from <shared library base address + ELF section
>> header offset>. As far as I'm aware, on Linux shared libraries aren't
>> required to be loaded in a contiguous block of memory, nor are the section
>> headers even required to be loaded in memory.
>> I was wondering if this is a know issue? If so is there a bug tracking
>> the progress?
>> Is remote debugging on Linux just not supported yet? Is this something
>> that is being actively worked on?
>> lldb-dev mailing list
>> lldb-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev