mdbell / Noexes

A graphical remote debugger for the Nintendo Switch
GNU General Public License v3.0
213 stars 53 forks source link

Game is Deallocating Memory Between Dumps, Causing Dumps to Fail #17

Open soliveau opened 5 years ago

soliveau commented 5 years ago

me.mdbell.noexs.core.ConnectionException: Result{mod=1, desc=106} at me.mdbell.noexs.core.Debugger.readmem(Debugger.java:274) at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:374) at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.refineSearch(MemorySearchService.java:214) at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:190) at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:175) at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source) at java.base/java.security.AccessController.doPrivileged(Native Method) at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)

soliveau commented 5 years ago

i wanted to double check EVERYTHING before leaving this, it happens to me on the latest 1.1.2 and 1.1.1.

mdbell commented 5 years ago

So you provided no context with what you were doing, but going by the provided error code (mod 1, desc 106, and using https://switchbrew.org/wiki/Error_codes#Error_codes to get it's meaning), you were refining a search and it gave you this exception... My best guess is that between the inital search and when you refined the game deallocated some memory (most likely by loading a new area), namely some memory we were trying to check.

If that is the case then this is a bug I need to fix. Can you confirm?

soliveau commented 5 years ago

yeah, sorry. i did in my initial post but not upon re-editing it... i should not post late at night.

it happens on the second search, every time. if i try another search after the second, it tries to dump about 400gigs. the game i was searching was south park: the fractured but whole.

ALETTERR commented 3 years ago

Can I ask if this problem can be solved

wobblemaster commented 1 year ago

Was this ever solved in the end? I'm getting the exact same problem so can't really do anything with the program. My error message is:

me.mdbell.noexs.core.ConnectionException: Result{mod=1, desc=106}
        at me.mdbell.noexs.core.Debugger.readmem(Debugger.java:274)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:373)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.refineSearch(MemorySearchService.java:211)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:187)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
        at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)