Definitely a bug. ValueObjectSynthetic overrides both GetChildMemberWithName
and GetIndexOfChildWithName so that if you have a synthetic value, it will look
in the synthetic children to match the name, not in the underlying value's
type. Not sure why this isn’t working.
Jim
> On Apr 7,
https://bugs.llvm.org/show_bug.cgi?id=45471
Bug ID: 45471
Summary: SymbolFileDWARF::ParseVariableDIE consider all
constant variables as "static"
Product: lldb
Version: unspecified
Hardware: PC
OS: All
3int main(int argc, const char **argv) {
4 std::atomic ai;
5 ai = argc;
-> 6 ai = argc + 1;
7 return 0;
8}
(lldb) fr var ai
(std::atomic) ai = {
Value = 1
}
(lldb) frame var --raw ai
(std::__1::atomic) ai = {
std::__1::__atomic_base = {
Hi Jonas, Davide,
I am not exactly thrilled by the ever-growing number of "modes" our test
suite can be run in. However, it seems that's a battle I am destined to
loose, so I'll just repeat what I've been saying for some time now.
I don't believe that either of these funny "modes" should be the
https://bugs.llvm.org/show_bug.cgi?id=45454
Bug ID: 45454
Summary: Race condition in debugserver stdout processing during
application exit.
Product: lldb
Version: 10.0
Hardware: PC
OS: All
Hi Davide,
I believe your guess about background processes is correct. I think that
the lldb process is stopped (or is continually getting stopped and
restarted) by SIGTTOU.
Macro: int SIGTTOU
This is similar to SIGTTIN, but is generated when a process in a
background job attempts to
