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

Investigate why an asynchronous signal is delivered mid-block #7081

Open
ivankyluk opened this issue Nov 13, 2024 · 0 comments
Open

Investigate why an asynchronous signal is delivered mid-block #7081

ivankyluk opened this issue Nov 13, 2024 · 0 comments

Comments

@ivankyluk
Copy link
Contributor

While investigating the Missing read/write records invariant error #7050, we found that asynchronous signal, i.e. SIGPROF, was delivered mid-block instead of at the end of a block.

Expected behavior
Signals which are marked as true in the can_always_delay array should be delivered at the end of a block instead of mid-block.

Versions

  • What version of DynamoRIO are you using? The latest.
  • Does the latest build from https://github.com/DynamoRIO/dynamorio/releases solve the problem? No.
  • What operating system version are you running on? ("Windows 10" is not sufficient: give the release number.) Linux Debian 6.9.10
  • Is your application 32-bit or 64-bit? 64 bit

Additional context
Xref #5063. There is drmemtrace discussion there: #5063 (comment). However, as that issue says, a regular asynch signal would be delayed and would be delivered in between the two blocks.

If this were a real interruption of a block: it would hit #5790 or #5063.

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

1 participant