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

> > When the branch is in good enough shape, hopefully by tomorrow, the > > first release candidate (RC1) will be tagged and testing can begin. > > The release schedule can be found under "Upcoming Releases" to the > > right at https://llvm.org > > > > Could you please do the necessary magic for 'r

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

On 20 Jul 2019, at 05:21, Tom Stellard via Release-testers wrote: > The 8.0.1 final release has been tagged. Testers please upload the final > binaries. As with 8.0.1 rc4, I had to disable compiler-rt for this test run, as most of the sanitizers are totally broken. This is tracked in PR40761.

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

I am still struggling with this issue. Now I decided to work with the codesigned version of the debugserver, becasue I had an error when I tried to use the system debugserver. So I've run scripts/macos-setup-codesign.sh After a reboot and fresh build (I have removed the CMakeCache.txt and the whole

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

> egbomrt@msmarple ~/llvm2/build/release_assert $ ./bin/lldb /bin/ls > (lldb) target create "/bin/ls" > Current executable set to '/bin/ls' (x86_64). > (lldb) r > *error: process exited with status -1 (Error 1)* I don't think this is related to debugserver codesigning. If you really need to debug s

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

Well, SIP is turned off and I experience the same with a binary I just built: ``` egbomrt@msmarple ~/llvm2/build/release_assert $ csrutil status System Integrity Protection status: disabled. egbomrt@msmarple ~/llvm2/build/release_assert $ ./bin/lldb ~/a.out (lldb) target create "/Users/egbomrt/a.ou

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

Interesting. Is there any extra info dumped to the log (e.g. `log enable lldb default`) On 22/07/2019 16:34, Gábor Márton wrote: > Well, SIP is turned off and I experience the same with a binary I just > built: > ``` > egbomrt@msmarple ~/llvm2/build/release_assert $ csrutil status > System Integri

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

Yes, here it is. egbomrt@msmarple ~/llvm2/build/release_assert $ ./bin/lldb ~/a.out (lldb) target create "/Users/egbomrt/a.out" Current executable set to '/Users/egbomrt/a.out' (x86_64). (lldb) log enable lldb default (lldb) r Processing command: r HandleCommand, cmd_obj : 'process launch' Hand

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

Some more info: I've stopped lldb (with the system lldb) when " Process::SetExitStatus (status=-1 (0x), description="Error 1")" is logged and gathered some more information. Is it possible that some packet types are not implemented? * frame #0: 0x7fff599452c6 libsystem_kernel.dylib`_

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

I think the system logs (in Console.app) would tell us more. Search for debugserver and you should find attach failures. Then remove the filter and look at what happens right before that. There should be a log from taskgated or authd that is a little more explicit about what’s failing. Fred >

[lldb-dev] ASTImporter Tutorial/TechTalk and RoundTable

Hi, I am planning to submit a talk about ASTImporter to the upcoming Dev Meeting at October 22-23, 2019. I'd like to talk about - the API, - how it is used in CTU analysis and in LLDB, - internal subtleties and difficulties (Error handling, ExternalASTSource, ...) The goal would be to attract more

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

Ok, I've done that, here are the logs which happen before the first debugserver error: error 18:33:20.236506 +0200 taskgated cannot open file at line 42270 of [95fbac39ba] error 18:33:20.236526 +0200 taskgated os_unix.c:42270: (2) open(/var/db/DetachedSignatures) - No such file or directory defaul

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

*error 18:33:20.280017 +0200 authd Fatal: interaction not allowed (session has no ui access) (engine 3727)* This gave me a hint, so I used VPN to have a gui and got a gui window popped up to authenticate lldb. And then I could run lldb as a normal user. Hurray! BUT through ssh I still cannot run l

Re: [lldb-dev] queue-name parameter

I already filed both of these issues with Apple. If you want to file them too, feel free. I'll dup them to the ones I filed but that way you will get notification when they get fixed. These are also general lldb issues, so it would be good to file something with http://bugs.llvm.org. Jim >

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

> On Jul 22, 2019, at 10:14 AM, Gábor Márton wrote: > > error 18:33:20.280017 +0200 authd Fatal: interaction not allowed (session > has no ui access) (engine 3727) > This gave me a hint, so I used VPN to have a gui and got a gui window popped > up to authenticate lldb. And then I could ru

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

On Fri, Jul 19, 2019 at 8:21 PM Tom Stellard via cfe-dev wrote: > > Hi, > > The 8.0.1 final release has been tagged. Testers please upload the final > binaries. Windows is ready: $ sha256sum *8.0.1-win*.exe 5d992a41f1ff6296659e66eabbcbaec34f5533fe9d1376fc94fba7450383fe69 LLVM-8.0.1-win32.exe e3

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

On Fri, Jul 19, 2019 at 4:08 PM Greg Clayton wrote: > Sounds like the compiler omitted the type info for std::string. Try "-glldb" > in your compiler flags. This tunes debug info for LLDB. A lot of compilers > will try to omit types from debug info if the type doesn't originate in the > curren

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

> On Jul 22, 2019, at 1:15 PM, Bob Eastbrook wrote: > > On Fri, Jul 19, 2019 at 4:08 PM Greg Clayton wrote: > >> Sounds like the compiler omitted the type info for std::string. Try "-glldb" >> in your compiler flags. This tunes debug info for LLDB. A lot of compilers >> will try to omit typ

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

I believe you can run a shell command as root: $ sudo /usr/sbin/DevToolsSecurity --enable Then you should be able to debug after that, even on ssh connections. Greg > On Jul 22, 2019, at 12:31 PM, Frédéric Riss via lldb-dev > wrote: > > > >> On Jul 22, 2019, at 10:14 AM, Gábor Márton >

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

On Mon, Jul 22, 2019 at 1:19 PM Greg Clayton wrote: > > Apparently the versions which ship with Ubuntu 19.04 and Fedora 30 differ > > with respect to this flag. > > So are you saying "-glldb" is wrong on Fedora but "-fno-limit-debug-info" > works? On Fedora 30: -g: no debug info -glldb: no de

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

> On Jul 22, 2019, at 1:53 PM, Bob Eastbrook wrote: > > On Mon, Jul 22, 2019 at 1:19 PM Greg Clayton wrote: > >>> Apparently the versions which ship with Ubuntu 19.04 and Fedora 30 differ >>> with respect to this flag. >> >> So are you saying "-glldb" is wrong on Fedora but "-fno-limit-debu

[lldb-dev] [Bug 20781] LLDB asserts "Cannot get layout of forward declarations!" from RecordLayoutBuilder.cpp:2782

https://bugs.llvm.org/show_bug.cgi?id=20781 Jonas Devlieghere changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 32100] [lldb] Member variables not updating using var objects

https://bugs.llvm.org/show_bug.cgi?id=32100 Jonas Devlieghere changed: What|Removed |Added CC||jdevliegh...@apple.com Resolution|-

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

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-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Thu, Jul 18, 2019 at 7:19 AM Hans Wennborg via Release-testers < releas