We'll be at Tied House as usual, starting on Thursday the 1st at 7pm!
If you can, help us plan and RSVP here:
https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyxdbcb/
See everyone there!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://l
Two way you can do this, the easy way, and the hard way.
The easy way is to allow a register to define a summary string that can be
attached to itself, just like "type summary add ...", but there is no typename
to associate here, you just give the summary a unique name. Type summaries
allow you
There isn't a built-in way to do this.
It would be nice to have "register {format, summary, synthetic children} add
{provider}" in parallel with the "type {format/summary/synthetic}
add".
The registers come to us as value objects so it would be straightforward to
hook them up, and the vario
Is there a way to define and display register fields, like gdb? Or would
this need to be done in python?
Example:
(gdb) p/x $vac0
$3 = {value = 0xedcba111, fields = {LENGTH = 0x111, SRC4_BANK = 0xa,
SRC3_BANK = 0xb,
SRC2_BANK = 0xc, SRC1_BANK = 0xd, DEST1_BANK = 0xe}}
--
Qualcomm Innovatio
> "Pavel" == Pavel Labath writes:
Pavel> To these very insightful emails from Greg and Jim, I'd just like to
Pavel> add one request. Please consider the testing strategy of the code you
Pavel> write early on. One of the problems that we have with these language
Pavel> plugins (and why we now
> "Jim" == Jim Ingham writes:
Jim> I naively thought this would make support for Rust weak, but folks
Jim> on Stack Overflow say it actually works pretty well for viewing
Jim> variables (using "frame var" or lldb's ValueObject's). Stepping
Jim> and so forth apparently seemed to be working ok
To these very insightful emails from Greg and Jim, I'd just like to
add one request. Please consider the testing strategy of the code you
write early on. One of the problems that we have with these language
plugins (and why we now have a separate thread considering removal of
some of them) is that
