Hi,
thank you for investigating this.
So, what you are describing should normally work. Generally
obj_file->GetDebugSymbolFilePaths() (SymbolVendorELF.cpp:99) should
return the correct name to look for the debug file. E.g., in my case
for libpthread it returns "libpthread-2.19.so", and indeed the
> I also checked the current HEAD of the lldb source tree to see if there are
> any changes, compared with my older revision. There is only a slight
> difference in how Symbols::LoadExecutableSymbolFile uses the /usr/lib/debug
> directory:
>
> // Some debug files may stored in the module direct
Hi Pavel,
I stepped through SymbolVendorELF::CreateInstance(), and it seems that
the problem lies within Symbols::LocateExecutableSymbolFile
(Host/common/Symbols.cpp). This method looks at the correct locations:
(gdb) print debug_file_search_paths
$35 = {m_files = std::vector of length 3, cap
You can also use SBCommandInterpreter::HandleCommand, which gives you
a bit more control over what happens.
good luck with your thesis.
pl
On 9 May 2016 at 10:00, Stefan Kratochwil wrote:
> Hi Pavel,
>
> thanks for your quick reply. I am currently using a release build, so it may
> take a momen
Hi Pavel,
thanks for your quick reply. I am currently using a release build, so it
may take a moment until I can step through there. I'll report back as
soon as possible (my masters thesis somehow depends on that ;) ).
I was just about to implement an addon for the API tonight, when I found
Hi Stefan,
what you are describing should work out of the box, so the fact that
you are having to add the symbols manually is a bug. I haven't tried
it with the apache binary specifically, but lldb can certainly find
external debug symbols for libc (definitely on ubuntu 14.04, as that's
what I use
Hi,
I need to gather information about variables on the stack frames of a
given program, lets say apache2 (httpd), using the C++ flavour of the
lldb scripting bridge.
Now, if I attach to the corresponding process id, lldb does not find any
debug symbols, although I have installed the debug s
