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

Revert "Revert (#2940)" #2973

Merged

Conversation

snehasish
Copy link
Contributor

This reverts commit 48db566 which
reverted the changes in PR #2940. The changes pushed caused some apps to
overflow the modidx field (issue #2956). PR #2969 increased the width of
the modidx field. We can now safely revert the revert.

This reverts commit 48db566 which
reverted the changes in PR DynamoRIO#2940. The changes pushed caused some apps to
overflow the modidx field (issue DynamoRIO#2956). PR DynamoRIO#2969 increased the width of
the modidx field. We can now safely revert the revert.
@snehasish
Copy link
Contributor Author

The failing Travis CI is due to an open issue (burst_threadfilter test failing with "Cannot correctly handle a received signal" #2941).

https://travis-ci.org/DynamoRIO/dynamorio/jobs/372579115

@derekbruening
Copy link
Contributor

Re-ran that build and now it's all green.

@derekbruening derekbruening merged commit 49e8db7 into DynamoRIO:master Apr 29, 2018
derekbruening added a commit that referenced this pull request Mar 10, 2021
PR #2940 and #2973 added an offset field to drmodtrack for #2939, but
they ifdef-ed the field in some places but not others, resulting in
uninitialized output.  Since it's already locked into the interface,
we always set it to 0 here and include it in internal structures to
fix the problem.

Tested on drmodtrack-test where the fields were manually confirmed to
no longer contain bogus values, and where the test doesn't fail when
that masked this bug before.

Issue: #2939, #4474, #4777
Fixes #4777
derekbruening added a commit that referenced this pull request Mar 10, 2021
PR #2940 and #2973 added an offset field to drmodtrack for #2939, but
they ifdef-ed the field in some places but not others, resulting in
uninitialized output.  Since it's already locked into the interface,
we always set it to 0 here and include it in internal structures to
fix the problem.

Tested on drmodtrack-test where the fields were manually confirmed to
no longer contain bogus values, and where the test doesn't fail when
that masked this bug before.

Issue: #2939, #4474, #4777
Fixes #4777
derekbruening added a commit that referenced this pull request Mar 10, 2021
PR #2940 and #2973 added an offset field to drmodtrack for #2939, but
they ifdef-ed the field in some places but not others, resulting in
uninitialized output.  Since it's already locked into the interface,
we always set it to 0 here and include it in internal structures to
fix the problem.

Tested on drmodtrack-test where the fields were manually confirmed to
no longer contain bogus values, and where the test doesn't fail when
i#4474 adds a new field that shifts the test buffer to avoid the
happens-to-match scenario that masked this bug in that test before.

Issue: #2939, #4474, #4777
Fixes #4777
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

Successfully merging this pull request may close these issues.

2 participants