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

re-enable tests: linux.vfork, linux.vfork-fib, win32.debugger, security-common.selfmod-big #125

Open
derekbruening opened this issue Nov 27, 2014 · 2 comments

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on April 13, 2009 09:57:06

several tests were disabled in the past. this case covers re-investigating
whether we can enable them now.

xref for vfork:
PR 207477 - Determina Case 2999: Linux regression failures: segfault and
vfork-fib
PR 209506 - Determina Case 5028: linux: re-enable vfork and signal nightly
tests once they don't hang/ruin machines

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=125

@derekbruening
Copy link
Contributor Author

From derek.br...@gmail.com on April 13, 2009 07:02:11

lumping these into this test too, to see if they work now and if not to file separate
Issues on the problems:

PR 209235 covers re-enabling selfmod-threads

PR 215238 covers re-enabling threadinjection

PR 199115 to re-enable fragdel

@derekbruening
Copy link
Contributor Author

From derek.br...@gmail.com on December 01, 2009 09:47:00

r249 re-enabled the basic vfork test for issue #237 and issue #229

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

No branches or pull requests

1 participant