nitesh.jain added inline comments.
Comment at: lldb/trunk/source/Plugins/Platform/Android/PlatformAndroid.cpp:389
+ struct __lldb_dlopen_result { void *image_ptr; const char
*error_str; } the_result;
+ the_result.image_ptr = __dl_dlopen ("%s",
Author: tberghammer
Date: Thu Jul 27 05:01:32 2017
New Revision: 309265
URL: http://llvm.org/viewvc/llvm-project?rev=309265&view=rev
Log:
XFAIL/XFlakey some tests what become very flakey on the Linux buildbot
Modified:
lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/concurre
Hi,
I have a question about the connection to a custom target with lldb. My
problem is:
i should create a debugger for code verification and fault injection on
a core architecture (synthesized on fpga) in which the compiler is LLVM
based. I think to use LLDB because the core target was just d
tberghammer added a comment.
Hi Nitesh,
The way dlopen, dlclose and dl_phdr_iterate is implemented on android is pretty
strange until (and including) SDK 25. The trick is that these functions are
implemented inside "/system/bin/linker" with actual function names prefixed
with "__dl_". The link
clayborg accepted this revision.
clayborg added a comment.
I'm ok as long as Pavel is ok. Please wait for the OK from him as well.
https://reviews.llvm.org/D33213
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bi
clayborg added a comment.
So the issue is with the ObjectFileELF when it makes its symbol table. It is
taking this symbols:
49686: bcf0 0 NOTYPE LOCAL DEFAULT 40 $debug_ranges627
And saying it is a code symbol. This symbols has a NOTYPE on it, not FUNC like
the main symbol. Fix t
clayborg added a comment.
maybe lldb::SymbolType::eSymbolTypeCompiler?
https://reviews.llvm.org/D35784
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
