Thanks!
On Sat, Jan 20, 2018 at 1:32 PM, Dimitry Andric wrote:
> On 19 Jan 2018, at 17:11, Hans Wennborg wrote:
>>
>> On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric wrote:
>>> On 18 Jan 2018, at 15:03, Jonas Hahnfeld wrote:
Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev:
>
Hi,
during my wandering I stumbled upon the `Go` and the `Java` plugins in
the lldb source tree.
They seem to not have been touched in a while, and I'm not necessarily
sure they're in a working state. Keeping them in tree is a maintenance
burden, so unless somebody is actively using them or somebod
The Go support for added by Ryan as a 20% project. Now that he's no
longer working for Google, it's pretty much abandoned.
The Java support was added by us (android folks) to support java
debugging (to a certain extent). However, we never really finished the
project, so we're not using that code no
To Davide's alternative: LLDB does handle loading plugins that use the SB API's
(for things like data formatters.) But there's not currently an SB interface
to support
writing a full language plugin, and we don't export the lldb_private API's from
the lldb binary. So there's no current mechan
Hi all,
I'm interested in understanding the why of LLDB, for that i'd love to be
able to read any meeting notes or slides of the BoF on the future of LLDB
and if possible make it available at [1] .
I'd also would like any indication of reading materials on the internals of
a debugger, preferabbly
https://bugs.llvm.org/show_bug.cgi?id=36048
Bug ID: 36048
Summary: TestDataFormatterLibcxxVector.py and
TestDataFormatterLibcxxVector.py fail with -fmodules
Product: lldb
Version: unspecified
Hardware: PC
OS
