-
Notifications
You must be signed in to change notification settings - Fork 566
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
drcachesim offline fails on fork child with error about file creation #5495
Comments
Xref a malloc check issue with fork (maybe that would be hit after this error is fixed): https://groups.google.com/g/dynamorio-users/c/D0HTG6dDIsY |
I see two further issues with
|
The first is a failure to remove the |
derekbruening
added a commit
that referenced
this issue
May 24, 2022
Fixes a bug where drcachesim -offline complained about an open file across a fork. This bug blocked tracing of SPECCPU perlbench. Adds a new test of drcachesim -offline with an app that forks. As is, this matched the -satisfy_w_xor_x test regex, and I tried to make it work with that option by fixing a file close bug here. However, I did not have time to figure out another bug which I filed as #5499. I thus tightened the "fork" regex to exclude this test from -satisfy_w_xor_x. Fixes #5495
derekbruening
added a commit
that referenced
this issue
May 25, 2022
Fixes a bug where drcachesim -offline complained about an open file across a fork. This bug blocked tracing of SPECCPU perlbench. Adds a new test of drcachesim -offline with an app that forks. As is, this matched the -satisfy_w_xor_x test regex, and I tried to make it work with that option by fixing a file close bug here. However, I did not have time to figure out another bug which I filed as #5499. I thus tightened the "fork" regex to exclude this test from -satisfy_w_xor_x. I also had to disable the malloc check and issue a warning for static link offline across fork due to the unsolved #4660. Issue: #5495, #5499, #4660 Fixes #5495
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I first hit this tracing SPEC2017 perlbench.
I can reproduce it easily:
The text was updated successfully, but these errors were encountered: