Better blacklisting, fixed exports #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hrydgard
added a commit
that referenced
this pull request
Nov 5, 2012
Better blacklisting, fixed exports
|
Nice work! |
Closed
Closed
Closed
5 tasks
ghost
mentioned this pull request
5 tasks
ghost
mentioned this pull request
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blacklisting is now based on the modules names, and not on PRXes name (way more efficient because games can actually name their PRXes like they want, even if it's a Sony module, whereas they can't change the module name).
Undecryptable PRXes (there are actually some missing keys for some sorts of kernel PRXes, probably for the ones included in games) are automatically blacklisted, so loading errors aren't taken in account.
I also fixed a stupid mistake I made with exports which should fix memory errors/segmentation faults.