An error occurred while fetching the assigned milestone of the selected merge_request.
- 22 Jan, 2020 5 commits
-
-
Derek Bruening authoredff6bf17b
-
Derek Bruening authored2848f7f3
-
Derek Bruening authoredab1a3d83
-
Derek Bruening authored
When a migration or context switch happens during rseq native execution, we now raise a kernel xfer event. The event is of a new type DR_XFER_RSEQ_ABORT. To implement this, the native abort handler cannot be linked and must return to dispatch. The special-exit-reason feature is used for this purpose. Adds a test. To force a migration we use a system call, which we do not normally allow inside an rseq region. I added a debug-build exception for this particular test by executable name, along with a syscall discovery workaround for the attach test. Adds a client via static DR to api.rseq to test that the event is raised. Adds handling to drmemtrace in the tracer and raw2trace. For raw2trace we walk backward to undo the committing store that was recorded, since a real rseq abort would happen before the final store. I would like to add on offline trace rseq regression test, but it hits Issue; #2350, #4019, #4041 Fixes #4019
aebad5bd -
Derek Bruening authored
Fixes an assert when we start building a trace but then have to abort due to the private copy failing. There is still a long-term problem here with the private copy failure potentially happening over and over: that is covered by #4038. Issue: #2989, #4038 Fixes #2989
9a0429e3
-
