LLDB's C++ API deals with SBxxx objects, most of which are PIMPL-style
wrappers around an opaque pointer to the internal implementation. These
SBxxx objects act as handles and are passed/returned by value, which is
generally convenient, except for the situations where one would need to
keep track o
https://bugs.llvm.org/show_bug.cgi?id=35652
Bug ID: 35652
Summary: Potential malware in test EXE
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priori
> On Dec 13, 2017, at 11:44 AM, Leonard Mosescu via lldb-dev
> wrote:
>
> LLDB's C++ API deals with SBxxx objects, most of which are PIMPL-style
> wrappers around an opaque pointer to the internal implementation. These SBxxx
> objects act as handles and are passed/returned by value, which is
https://bugs.llvm.org/show_bug.cgi?id=35654
Bug ID: 35654
Summary: LLDB Does not print the correct value for a variable
(suspect NRVO alias issue)
Product: lldb
Version: unspecified
Hardware: Macintosh
OS: M
Thanks Greg,
1. Expose the opaque ptr as an opaque handle()
- this is an easy, quick and convenient solution for many SBxxx types
but it may not work for all
That would be nice, but that won't always work with how LLDB is currently
> coded for SBFrame and possibly SBThread. These objects wil