-
Notifications
You must be signed in to change notification settings - Fork 6
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
mscorlib error #14
Comments
Hi, Due to the fact that the previous version of the program did not display detailed errors when encountering exceptions during Scan Task execution, I couldn't ascertain the actual cause of the issue you experienced. Below, I have made a version change that enhances the display of error messages for ScanTask in the Query window. Although this problem hasn't been resolved yet, it can provide me with more information about the errors that occur. Thank you. |
Ok after the 9.8.8 patch here's the more detailed error I've encountered.
|
First of all, thank you for quickly testing and providing the new error message. After reviewing the content, the most likely place where the error occurred appears to be "[at PS4CheaterNeo.PS4Tool.ReadMemory]." This section involves reading memory data from the PS4 to the PC using the ps4debug tool. Due to the lack of a more detailed error reason, I'm unsure about what exactly went wrong here. Could you provide your PS4 version and the version of ps4debug you are using? |
Upon reviewing the error logs once again, I thought that "The wait completed due to an abandoned mutex." could also be a potential cause of errors during scanning. I referenced "Understanding AbandonedMutexException in Multithreading" and "Good pattern for using a Global Mutex in C#?" and made modifications to the PS4Tool, SectionTool, and HexEditor class that use Mutex syntax. While I hope that this will prevent AbandonedMutexException errors, I cannot replicate the same error in my environment, so I'm uncertain about its effectiveness. Please assist in verifying this. Thank you. |
I'm on firmware 9.00 using ps4debug 1.0.15
|
The main cause of this error message is "PS4DBG is not connected." In version 0.9.9.1-beta, I have added a feature to attempt reconnection when PS4Tool's ConnectedCheck detects that PS4DBG is not connected. It may not always be effective, as when PS4DBG is not connected, it may not be a simple fix through reconnection. Please test it to see if it works. Thank you. |
New error, also sorry for the inactivity. I'm available now to give you information consistently.
|
I'm sorry, but I feel powerless to handle this part because it's an error message coming directly from ps4debug itself. In general, such errors shouldn't occur... |
As Avan06 said this is no an issue with his tool... |
When scanning through the memory, I come across this issue.
The text was updated successfully, but these errors were encountered: