Re: [lldb-dev] [Release-testers] [cfe-dev] 8.0.1-final has been tagged

2019-07-23 Thread Diana Picus via lldb-dev
ARM & AArch64 ready: c87b57496f8ec0f0fd74faa1c43b0ac12c156aae54d9be45169fd8f2b33b2181 clang+llvm-8.0.1-armv7a-linux-gnueabihf.tar.xz a80dc5ca8d9bf5dfb12502263fd50bde6260fe661c1d1f6fb88c7a1146c879f4 clang+llvm-8.0.1-aarch64-linux-gnu.tar.xz Cheers, Diana On Mon, 22 Jul 2019 at 21:40, Hans Wennborg

Re: [lldb-dev] "error: summary string parsing error" on Fedora 30

2019-07-23 Thread via lldb-dev
Behavior of the -g variants is probably better discussed on llvm-dev. --paulr > -Original Message- > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Greg > Clayton via lldb-dev > Sent: Monday, July 22, 2019 5:38 PM > To: Bob Eastbrook > Cc: lldb-dev@lists.llvm.org > Su

Re: [lldb-dev] Cannot use system debugserver for testing

2019-07-23 Thread Gábor Márton via lldb-dev
> $ sudo /usr/sbin/DevToolsSecurity --enable Unfortunately, this did not help. Anyway, I've found the solution, but took a while. So, the given scripts/macos-setup-codesign.sh adds a certificate to the system keychain /Library/Keychains/System.keychain and with a TrustRoot policy. This explains wh

[lldb-dev] test suite issue with Python2.7/3.5

2019-07-23 Thread Romaric Jodin via lldb-dev
Hi everyone, I'm trying to run the test suite on lldb and I'm having some issues with Python. I'm on branch 7.0. When I build lldb, I've got a folder "python3.5/site-packages" generated. So I believe that the build system found python3 in my environment. But when I run the testsuite (using "ninja

Re: [lldb-dev] test suite issue with Python2.7/3.5

2019-07-23 Thread Jonas Devlieghere via lldb-dev
The 7.0 branch is not compatible with Python 3, at least not if you're not on Windows. The first release that is, would be 9.0, which is currently being qualified. This includes a bunch of compatibility fixes, and a newer version of the vendored pexpect (4.6). As you've noticed, using different ver

Re: [lldb-dev] [Release-testers] 8.0.1-final has been tagged

2019-07-23 Thread Brian Cain via lldb-dev
[previously I misdirected this message as a reply to the 9.0.0 thread, so I'm reproducing here just in case] Uploaded ubuntu 14. I had to kill some tests executing "lldb-vscode", they had been running for 12+ hours without completing. b57383860c7e4317b0194d1a91836e01bd637c95 clang+llvm-8.0.1-x8

[lldb-dev] [Bug 42724] New: lldb fails to build on windows with RegisterContextWindows_x64.cpp(297): error C2039: 'Rax': is not a member of '_CONTEXT'

2019-07-23 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=42724 Bug ID: 42724 Summary: lldb fails to build on windows with RegisterContextWindows_x64.cpp(297): error C2039: 'Rax': is not a member of '_CONTEXT' Product: lldb Version:

Re: [lldb-dev] [Release-testers] [9.0.0 Release] The release branch is open; trunk is now 10.0.0

2019-07-23 Thread Ted Woodward via lldb-dev
We saw the same thing internally. We don’t use lldb-vscode, so we turned off those tests. Greg, any thoughts on lldb-vscode tests running forever on Linux? From: lldb-dev On Behalf Of Brian Cain via lldb-dev Sent: Monday, July 22, 2019 10:44 PM To: Hans Wennborg Cc: llvm-dev ; Release-testers

Re: [lldb-dev] [Release-testers] [9.0.0 Release] The release branch is open; trunk is now 10.0.0

2019-07-23 Thread Greg Clayton via lldb-dev
Maybe https://reviews.llvm.org/D65163 will fix this issue? > On Jul 23, 2019, at 11:57 AM, Ted Woodward wrote: > > We saw the same thing internally. We don’t use lldb-vscode, so we turned off > those tests. > > Greg, any thoughts on lldb-vscode tests running

[lldb-dev] Evaluate expression for template class

2019-07-23 Thread Scott Funkenhauser via lldb-dev
Hey, I've noticed that evaluating expressions involving templated classes seems to have some unexpected behavior. I've created the following sample code to reproduce the issue: template class foo { uint32_t data; }; foo test; int main() { foo test2; return 0; } I've set a breakpoint on

Re: [lldb-dev] Evaluate expression for template class

2019-07-23 Thread Jim Ingham via lldb-dev
lldb can't currently create new template instantiations. It can only access ones that were generated in the binary you were debugging. The debug information doesn't have any code, so we can't create new instantiations from there. Having the debugger try to include headers into the expression

Re: [lldb-dev] Evaluate expression for template class

2019-07-23 Thread Scott Funkenhauser via lldb-dev
I built with both clang and gcc, the behavior is the same (lldb fails to evaluate the expression, gdb succeeds). Trying to evaluate a template type that hasn't been instantiated fails in both lldb and gdb. ie. (gdb) p sizeof(foo) No symbol "foo" in current context. (lldb) p sizeof(foo) error: impl

Re: [lldb-dev] Evaluate expression for template class

2019-07-23 Thread Jim Ingham via lldb-dev
Interesting... What lldb & clang were you using? With current TOT clang & lldb I see: (lldb) run Process 83732 launched: '/tmp/template2' (x86_64) Process 83732 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1 frame #0: 0x00010fad template2`main at

Re: [lldb-dev] [Release-testers] 8.0.1-final has been tagged

2019-07-23 Thread Brian Cain via lldb-dev
Uploaded SLES11. a18ac0820acf7e4b19b917a143868a73ddb30a02 clang+llvm-8.0.1-x86_64-linux-sles11.3.tar.xz On Tue, Jul 23, 2019 at 10:10 AM Brian Cain wrote: > [previously I misdirected this message as a reply to the 9.0.0 thread, so > I'm reproducing here just in case] > > Uploaded ubuntu 14. >