\On Sat, May 29, 2021 at 10:57 PM Raphael Isemann
wrote:
> And I think the best way to propose a new API is maybe just making a
> dummy patch that adds the API + documentation (doesn't need an actual
> implementation or tests). And if everyone agrees the new API is fine
> you can add the tests
Hello,
I've recently been working on and with my Rust bindings to the public LLDB
API after a break of a couple of years.
A couple of things that I'm noticing or re-noticing:
We need more SB API coverage of logging functionality. We can't list
channels, categories via the SB API. We also don't
I like this a lot!
I commented on the patch since I didn't see this thread at the time, but
it'd be interesting to perhaps replace Epydoc with Sphinx as well.
- Bruce
On Fri, Dec 7, 2018 at 12:02 AM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi everyone,
>
> The
Hello,
I was adding support for `SBStructuredData` to my Rust bindings for the
LLDB API and noticed a couple of things.
Since 5.0 isn't out yet and these are newer API additions, I was hoping
there might still be time to fix this.
`SBStructuredData::GetFloatValue` returns a `double`, but other
Hello,
SBAttachInfo exposes a bunch of getters and setters for user ID, groupID,
parent process ID, effective user ID, effective group ID.
It doesn't seem like one would set these to anything prior to attaching,
but I also don't see in the code where they might get set in the event of a
Hello all,
I've been working on Rust bindings for the LLDB API and they're coming
along pretty well. They aren't complete yet, but they're getting close:
https://github.com/endoli/lldb.rs/
The documentation for these bindings can be found at
https://endoli.github.io/lldb.rs/
I need to write
Stepping one step back further in the thread ...
On Wed, Nov 18, 2015 at 8:35 AM, Zachary Turner via lldb-commits <
lldb-comm...@lists.llvm.org> wrote:
> Moving this back over to the list since I'm sure others have some input
> here. Also +lldb-dev since it has more visibility than
Greg et al:
When linking (cmake on OS X), I get a lot of warnings like this:
ld: warning: cannot export hidden symbol lldb::endian::InlHostByteOrder()
from
lib/liblldbPluginProcessUtility.a(RegisterContextDarwin_arm64.cpp.o)
Should this function be in the public namespace?
It is an
to pick up the LLVM_LIBRARY_VISIBILITY definition. Would
we be able to put that in one of the LLDB headers that is already included
everywhere?
- Bruce
On Fri, Aug 14, 2015 at 11:14 PM, Greg Clayton gclay...@apple.com wrote:
On Aug 13, 2015, at 6:43 PM, Bruce Mitchener via lldb-dev
