Michael Buch

CC @vogelsgesang @walter-erquinigo since they're more familiar with the DAP infrastructure than me. Any idea why we might fail to launch the test executable in a container (inside a container)?

Interestingly, looks like @mordante has run into this before with the data-formatter CI: * https://discourse.llvm.org/t/running-lldb-in-a-container/76801 * https://github.com/llvm/llvm-project/pull/88312 Though the fix for it doesn't seem to work for this case?

> > Any idea why we might fail to launch the test executable in a container (inside a container)? > > You need to set up the debug session with...

> Thanks a lot for chiming in! Side question: I thought ASLR was the problem, so shouldn't the solution be to **turn off** ASLR, i.e. use `settings set target.disable-aslr true`?...

https://github.com/llvm/llvm-project/pull/113593 If you want to make sure that this definitely resolves the issue @EricWF, you could cherry-pick that change and let the PR CI run again?

> Thanks for your fast help with this. Re-basing and rerunning now. Np! Haven't merged it yet though. Just waiting for CI to pass

Hmm am I reading this right that the latest run still failed, despite the cherry-pick? EDIT: Oh nvm, the change didn't seem to kick in yet: ``` { "arguments": {...

FYI, had to adjust the flag in one other place. Feel free to rebase the branch on `main`. I merged the changes. Let me know if the CI still fails

> It looks like it's still failing with the latest run :-( Argh that's unfortunate. How about we skip this test in libc++ CI to unblock this PR and I'll...

> > > It looks like it's still failing with the latest run :-( > > > > > > Argh that's unfortunate. How about we skip this test in...