https://llvm.org/bugs/show_bug.cgi?id=27515
Greg Clayton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
> So the main question is why is anything that is indexing the current CU only,
> accessing anything from another CU? It can't and shouldn't. That is the bug.
Indexing is accessing another CU because there is a reference (offset) to
another CU.
For example, in the 2nd compile unit below, the D
As Tamas said, little effort has gone into the to stabilization of the
3.8 branch. Right now, you're the only one looking into it, so I think
we'll just defer to your judgement. It is a bit of a duplication of
effort but, I think it is very worthwhile for lldb project as a whole.
For the multithre
Hi all. First post...new to the mailing list.
I was looking for the lldb/branches/google/stable/ branch on a git mirror, but
was unable to find it. I was specifically looking at
http://llvm.org/git/lldb.git, but didn't see it anywhere else either (github,
etc).
Is it only available from the sv
I needed to have a (recent) branch of lldb which was stable for debugging
across platforms (native darwin, native linux, android, etc). I originally
tried using the google/stable branch (which I assume is what ships with
Android Studio), but that had some crashes with darwin debugging. I had
assume
> On Apr 28, 2016, at 8:11 AM, Philippe Lavoie
> wrote:
>
>
> What made me suspect a data corruption issue were asserts triggered in the
> VC++ vector implementation when we use an LTO binary with a DEBUG lldb build
> on Windows.
>
> For example,
> at source/Plugins/SymbolFile/DWARF/DW
Is there any reason you want to use the release_38 branch specifically? As
far as I know nobody tested it or using it in the LLDB community so it is
approximately as good as any random commit on master. If you are looking
for a reasonably stable LLDB then I think you are better off with asking
for
