[lldb-dev] [5.0.0 Release] Release Candidate 3 tagged

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues

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 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,

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

> -Original Message- > From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf > Of Hans Wennborg > Sent: 24 August 2017 22:50 > To: Simon Dardis > Cc: Release-testers; llvm-dev; cfe-dev; openmp-dev (openmp- > d...@lists.llvm.org); LLDB Dev > Subject: Re: [cfe-dev] [5.0.0

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Only 3 release blockers left, please help fix!

> -Original Message- > From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of Hans > Wennborg via llvm-dev > Sent: Thursday, August 24, 2017 6:06 PM > To: llvm-dev; cfe-dev; LLDB Dev; openmp-dev (openmp-...@lists.llvm.org) > Subject: [llvm-dev] [5.0.0 Release] Only 3

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

I found a hang in lldb-mi's -var-update. It checks to see if a var changed, then it checks each of the children recursively. If a child is a pointer back to a parent, as in this case: struct complex_type { int i; struct { long l; } inner; struct complex_type *complex_ptr; }; void

Re: [lldb-dev] Remote debugging ARM target from x86 host

Maybe we can make it open only an IPv4 socket for lldb-server for now as a work around? > On Aug 25, 2017, at 8:47 AM, Chris Bieneman wrote: > > Since lldb-server only supports running on a limited set of host operating > systems it is hard for me to diagnose the issue

Re: [lldb-dev] Remote debugging ARM target from x86 host

Since lldb-server only supports running on a limited set of host operating systems it is hard for me to diagnose the issue completely, but I suspect the problem is caused by the fact that the new listening code can open more than one socket, and TCPSocket::GetLocalPortNumber() may be