forked from yck1509/ConfuserEx
-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Application crashed due to Failed to rename all targeted members, because the references are blocking each other
#379
Comments
KvanTTT
added
potential-bug
Something does not seem to be working
triage
This issue needs some initial analysis.
labels
Jul 17, 2021
KvanTTT
changed the title
The error
Application crashed due to Jul 17, 2021
Failed to rename all targeted members, because the references are blocking each other
is still presented in the latest versionFailed to rename all targeted members, because the references are blocking each other
KvanTTT
added a commit
to PositiveTechnologies/ConfuserEx
that referenced
this issue
Jul 25, 2021
Unfortunately, I was not able to find a minimal sample that covers this issue. But I found out how to fix it, please check the related pull request. |
mkaring
added
bug
Something isn't working
and removed
potential-bug
Something does not seem to be working
triage
This issue needs some initial analysis.
labels
Aug 13, 2021
KvanTTT
added a commit
to PositiveTechnologies/ConfuserEx
that referenced
this issue
Aug 15, 2021
KvanTTT
added a commit
to PositiveTechnologies/ConfuserEx
that referenced
this issue
Aug 15, 2021
It seems like I've found such a sample (see in the attached pull request)! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Confuser displays the error during confusing (by yellow color):
But application crashes with a similar exception (these definitions match definitions from the abovementioned warning message):
This probably happens due to renaming protection with
renPublic = true
and related to cases when the method in base type implements an interface method for the derived type.shortNames
option does not help.I'll try to extract a minimal code sample later (it's quite complicated because of the big project and intertwined structure).
Is it possible to fix it (it worked in previous versions)? Or similar entities should be excluded from renaming?
The text was updated successfully, but these errors were encountered: