Re: [lldb-dev] [5.0.0 Release] Release Candidate 2 source and binaries available

Hi all, I've uploaded the mips binaries: SHA1(clang+llvm-5.0.0-rc2-mipsel-linux-gnu.tar.xz)= 56366fdcaec1ce77d7b481ff74f6d4132b3219d7 SHA1(clang+llvm-5.0.0-rc2-mips-linux-gnu.tar.xz)= 8b66db0b4fe3e5d288ee6ac32621bdfdbc9e3233 SHA1(clang+llvm-5.0.0-rc2-x86_64-linux-gnu-debian8.tar.xz)= 5dc458993

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 2 tagged

On Thu, Aug 17, 2017 at 4:03 PM, Vedant Kumar wrote: > Hi, > > There are no regressions from RC1 on Darwin. > > I've uploaded clang+llvm-5.0.0-rc2-x86_64-apple-darwin.tar.xz to > /data/testers-uploads. > > SHA 1: 8ffaf7ab44e7e7fe582dc9573aad9745ee63e186 > SHA 256: 578c18ceb6485fd2fcac329a7a5fe7e5

Re: [lldb-dev] [5.0.0 Release] Release Candidate 2 source and binaries available

Thanks! I've added the binaries to the pre-release page. On Fri, Aug 18, 2017 at 8:44 AM, Simon Dardis wrote: > Hi all, > > I've uploaded the mips binaries: > > SHA1(clang+llvm-5.0.0-rc2-mipsel-linux-gnu.tar.xz)= > 56366fdcaec1ce77d7b481ff74f6d4132b3219d7 > SHA1(clang+llvm-5.0.0-rc2-mips-linux-g

[lldb-dev] [5.0.0 Release] Please write release notes

Dear everyone, We're a couple of release candidates into the process, and the release notes are not in very good shape: http://prereleases.llvm.org/5.0.0/#rc2 If you committed anything noteworthy in the last six months, or saw someone else do it, please consider adding it to the release notes. Pe

[lldb-dev] Forcing lldb to refresh process state

Hi, Is there any way to force lldb to refresh it's internal record of debuggee process state (as if it had just received a stop event)? I want to send a custom command to remote gdb process stub (via `process plugin packet send`). This works, but if the command alters debuggee state, lldb won't k

Re: [lldb-dev] Forcing lldb to refresh process state

No, there hasn't been a need for this. What commands are you planning to send? Or equivalently, how much state are you expecting to change? Jim > On Aug 18, 2017, at 4:36 PM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > Is there any way to force lldb to refresh it's internal record of d

Re: [lldb-dev] Forcing lldb to refresh process state

I'm trying to reverse-step. So I think I'd need to refresh all thread states? > On Aug 18, 2017, at 4:50 PM, Jim Ingham wrote: > > No, there hasn't been a need for this. > > What commands are you planning to send? Or equivalently, how much state are > you expecting to change? > > Jim > >