Re: [lldb-dev] hang bug in lldb-mi -var-update

2017-08-28 Thread Greg Clayton via lldb-dev
py when it doesn't :-) >> >> Ted >> >> -- >> Qualcomm Innovation Center, Inc. >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a >> Linux Foundation Collaborative Project >> >>> -Original Message----- >&

Re: [lldb-dev] hang bug in lldb-mi -var-update

2017-08-25 Thread Jim Ingham via lldb-dev
member of Code Aurora Forum, a > Linux Foundation Collaborative Project > >> -Original Message- >> From: Greg Clayton [mailto:clayb...@gmail.com] >> Sent: Friday, August 25, 2017 5:00 PM >> To: Ted Woodward >> Cc: lldb-dev@lists.llvm.org >> Subject: Re:

Re: [lldb-dev] hang bug in lldb-mi -var-update

2017-08-25 Thread Ted Woodward via lldb-dev
clayb...@gmail.com] > Sent: Friday, August 25, 2017 5:00 PM > To: Ted Woodward > Cc: lldb-dev@lists.llvm.org > Subject: Re: [lldb-dev] hang bug in lldb-mi -var-update > > lldb-mi should never be checking the children. This is never a good idea due to > performance. What happen

Re: [lldb-dev] hang bug in lldb-mi -var-update

2017-08-25 Thread Greg Clayton via lldb-dev
lldb-mi should never be checking the children. This is never a good idea due to performance. What happens when you have an array with a million entries? Long delay. Aggregate types should never say they changed. Only SBValue objects that have values should claim to change. Greg > On Aug 25, 2