Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch_DebuggerIsAttachedPosix failure #149

Open
marsupial opened this issue Jan 13, 2017 · 2 comments
Open

Arch_DebuggerIsAttachedPosix failure #149

marsupial opened this issue Jan 13, 2017 · 2 comments

Comments

@marsupial
Copy link
Contributor

Description of Issue

Arch_DebuggerIsAttachedPosix can return true in cases where the process is in fact not being debugged (on OS X always and on Linux when YAMA trace_scope is enabled). This will hang after a crash as it assumes the process is being traced. Fixed on OS X by testing if debugger is attached according to Apple docs, and on Linux by making sure the forked child has permission to attach.

Steps to Reproduce

  1. Run testTfSIGSEGV SIGSEGV on OS X or Ubuntu Trusty. Or call Arch_DebuggerIsAttachedPosix on either platform and it will always return true.

System Information (OS, Hardware)

OS X & Ubuntu Linux.

Pull requests #148 fixes this.

@jtran56
Copy link

jtran56 commented Jan 13, 2017

Filed as internal issue #141902.

@marsupial
Copy link
Contributor Author

For what its worth, the pull request was tied to incorrect commits to fix this issue.
That has been corrected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants