[lldb-dev] Supporting new source languages

[Todd Fiala]

We haven't done any research on it yet, but at some point we were going to
look at some minimal support for showing useful backtrace info when on
Android and the back trace hops over a JNI boundary (i.e. into/out of Java,
possibly multiple times), particularly when lldb is stopped in native C/C++
code.  I'm not sure how much (if any) Java language handling we'll do,
since the most basic application of back-trace context probably only needs
to handle looking up symbols on the JVM side.  If we wanted to handle
variable lookup and similar handling that needs to deal with expressions,
we'll probably start caring about this as well.


On Thu, Jan 16, 2014 at 8:10 AM, Bruce Mitchener
<bruce.mitchener at gmail.com>wrote:

> On Thu, Jan 16, 2014 at 11:04 PM, Michael Woerister <
> michaelwoerister at posteo.de> wrote:
>>
>> Nobody care to comment? Let me elaborate a bit on my reasons for asking.
>> Since last summer I've been working on debuginfo generation for the Rust
>> compiler (www.rust-lang.org). As the Rust compiler is LLVM based this
>> worked out pretty well and we produce DWARF good enough to satisfy basic
>> debugging needs. However, obviously debuggers don't recognize Rust yet and
>> print out values in the wrong syntax among other things. Some of this can
>> be alleviated with Python extensions in LLDB and GDB, but the information
>> available through those APIs seems to be limited (eg. it seems hard get
>> modifiers, such as 'const' or 'volatile'). Also it would be great to allow
>> for parsing Rust expressions in the debugger, call functions, in short:
>> make Rust a first-class citizen of the given debugger. I'm currently trying
>> to find out what the possibilities in this area are.
>>
>> GDB seems to have a story for supporting new source languages but for
>> LLDB I couldn't find anything about the topic yet. It would be great if
>> somebody could elaborate on this, even if only saying "not a goal for LLDB"
>> or "too early to ask for something like this".
>>
>
> This is something that we'll be interested in as well in the Dylan (
> http://opendylan.org) community sometime in 2014 once we get our LLVM
> backend functional.
>
>  - Bruce
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>


-- 
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140116/f44bb5af/attachment.html>