+Tom who owns the 3.8.1 release
On Tue, May 3, 2016 at 10:04 AM, Francis Ricci via lldb-dev
wrote:
> I didn't have any luck with r266423, these dwarf issues can get pretty
> tricky.
>
> Ok, that makes sense. We've been using these commits on top of our
> release_38 branch for several weeks now, a
I didn't have any luck with r266423, these dwarf issues can get pretty
tricky.
Ok, that makes sense. We've been using these commits on top of our
release_38 branch for several weeks now, and I'm happy with their
stability. I'll continue to be on the lookout for bugs and bug-fixes.
Hans, can we ge
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
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
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
Over the last month or two, I've been working to stabilize the release_38
branch of lldb, and there are commits which fix bugs on this branch that
I'd like to cherry-pick down. They're listed at the bottom of this message.
One thing to note - r251106 is a commit I'd like to revert, instead of a
ch
