https://llvm.org/bugs/show_bug.cgi?id=27634
Bug ID: 27634
Summary: Spelling fixes for lldb
Product: lldb
Version: 3.8
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P
We aren't qualifying it on our side so it hasn't gotten a stable/testing
set of branches.
-eric
On Tue, May 3, 2016 at 4:15 AM Tamas Berghammer via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> +Eric Christopher
>
> Adding Eric as he was the last person merging changes to
> On May 3, 2016, at 6:35 AM, Philippe Lavoie
> wrote:
>
> The code accessing another CU while indexing is in DWARFCompileUnit::GetDIE.
> If the DIE is not in the current CU, it finds the CU that has it and calls
> its ::GetDIE method, accessing its m_die_array
The code accessing another CU while indexing is in DWARFCompileUnit::GetDIE.
If the DIE is not in the current CU, it finds the CU that has it and calls its
::GetDIE method, accessing its m_die_array data...
So the question is: is it a producer (CU should be self-contained) or a
consumer (the
+Eric Christopher
Adding Eric as he was the last person merging changes to the google/stable
branch. As far as I know nobody releases LLDB from that branch so I
wouldn't rely on it too much (Android Studio release from master) but you
can gave it a try if you want.
Tamas
Since I am working on debugger support for OCaml, I am dealing with symbols of
the following form:
camlFoo__bar_1010
The function name is prefixed with the "caml" followed by the local module
name. OCaml is using a dot instead of a double colon to access function within
a module, and is