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). We need to
what is different in your case. The
most important function here is SymbolVendorELF::CreateInstance. Could
you step through that function, and see why it fails to find the file?
On 7 May 2016 at 19:45, Stefan Kratochwil via lldb-dev
wrote:
Hi,
I need to gather information about variables on
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
, Stefan Kratochwil via lldb-dev
wrote:
Hi altogether,
I currently am developing an application where I need to access the DWARF
debugging information of my target process and its loaded .so files.
In more detail, I need to match type information of certain entities within my
code and its
Hi,
well, I found the llvm-dwarfdump tool in the tools directory *facepalm*...
I'll use that as a reference.
That leaves the question about the two separate DWARF implementations.
Cheers,
Stefan
On 10/13/2015 11:42 AM, Stefan Kratochwil via lldb-dev wrote:
Hi altogether,
I current
Hi altogether,
I currently am developing an application where I need to access the
DWARF debugging information of my target process and its loaded .so files.
In more detail, I need to match type information of certain entities
within my code and its dynamically linked libraries.
I already
Hi,
I am wondering how to deal with binaries that are both executable and
dynamic objects, such as many executables under /usr/sbin.
When I try to attach to a process (e.g. apache2) using the method
lldb::SBTarget::AttachToProcessWithID() (C++ flavor of the LLDB
ScriptingBridge), the method Objec
to a bug in llvm.org/bugs.
I am currently using svn revision 247535 of llvm and lldb, and I know that my
code was working with svn revision 229496
This sounds like a pretty big revision range. It would help if you
could narrow it down a bit.
pl
On 28 September 2015 at 09:12, Stefan Kratochwi
Hi,
I've got a problem with lldb deadlocking upon a call to
lldb::SBDebugger::Terminate().
I am currently using svn revision 247535 of llvm and lldb, and I know
that my code was working with svn revision 229496.
In short, I am doing the following steps:
lldb_debugger = lldb::SBDebugger::
