Some tests in LldbGdbServer.py are flaky

[sas]

Here's a failing test output: https://gist.github.com/sas/b0dcd8f59793a6801515a8e7d0d19c8e

[kokarez]

Not fully sure, I've base my research on:

[20925][Target::Process::Attach] ERROR  : ptrace attach failed: Operation not permitted

This was weird until I've read that: Ubuntu PTrace Protection

From that doc, set ptrace_scope to 0 could solve this issue.

[sas]

That's really surprising, given that all other tests work fine.

On Thu, May 12, 2016 at 3:27 PM, kokarez notifications@github.com wrote:

Not fully sure, I base my research on:

[20925][Target::Process::Attach] ERROR : ptrace attach failed: Operation not permitted

This was weird until I've read that: Ubuntu PTrace Protection
https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection

From that doc, set ptrace_scope to 0 could solve this issue.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#341 (comment)

Stephane Sezer

[kokarez]

Yea, and it's an intermittent issue. But, I don't see how we can get a 'Operation not permitted' randomly on only one test

[sas]

I'd expect a timing issue. Like we try attaching to something before we're
supposed to, or something like that.

I'd be really surprised if the value of ptrace_scope were to change
randomly during execution.

On Thu, May 12, 2016 at 3:40 PM, kokarez notifications@github.com wrote:

Yea, and it's an intermittent issue. But, I don't see how we can get a
'Operation not permitted' randomly on only one test

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#341 (comment)

Stephane Sezer