Dear testers,
8.0.0-rc2 has been tagged from the release_80 branch at r353413.
Please run the test script, share your results, and upload binaries.
I'll get the source tarballs and docs published as soon as possible,
and binaries as they become available.
Thanks,
Hans
__
https://bugs.llvm.org/show_bug.cgi?id=40588
lab...@google.com changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |lab...@google.com
Resolution|---
On 06/02/2019 23:11, Joshua Peraza via lldb-dev wrote:
Adding a hashes where we need them SGTM.
I think that's a reasonable approach. We can decide on the best hash and
equality functions on a case-by-case basis.
___
lldb-dev mailing list
lldb-dev@
Hello all,
currently I am at at stage where the only large piece of functionality
missing from the Breakpad symbol file plugin is the unwind information.
The PDB plugin has been in that state for a while. I'd like to rectify
this situation, but doing that in the present lldb model is somewhat
We also have information that is generated, like assembly unwind, ABI plug-ins
(I believe) which give out the arch defaults for how to unwind at the first
instruction of the function, and also one that unwinds when you are in the
middle (follow the frame pointer and PC is at FP-). It would be gr
Hi Pavel,
I'm open to this. I don't think there was any specific reason why UnwindTable
is in the ObjectFile over the Module - it was very likely not an intentional
choice when I put it there.
To recap, each "binary" in the system has an UnwindTable. The UnwindTable has a
list of functions it
