search

korcankaraokcu / PINCE

Reverse engineering tool for linux games
Other
2.13k stars 149 forks source link

Problem with scan in "unknown value" mode #256

Closed X-Keyscore closed 6 months ago

X-Keyscore commented 6 months ago

When I am specifically in this mode, the search launches then the PINCE.sh console indicates killed after that the program exits and the target remains open and usable. I was told in another issue that it was the target that was preventing debugging but I'm not sure that's what's happening here.

Didn't see any gdb error. Probably because it is not affected by this action but I admit that I have difficulty understanding how the pince works.

When I use the exact mode everything goes well.

(sorry for the spam but I can't find any info elsewhere)

Bloodiko commented 6 months ago

"Killed" means, your process, in this case the scanmem sub-process of pince or maybe also pince as parent process, got killed due to the system beeing oom (out of memory), which will trigger a system response by killing the process.

Try searching something less broad, for example you could use "in between" which does result in far less results. Also, if possible, keep it above or below 0 if possible, because on large processes, 0 will produce massive amounts of results potentially, which are most likely useless.

But the memory issue is definitely something we might need to address at some point.

X-Keyscore commented 6 months ago

ok thank you for the response, I have already tried between but I did not think that 0 was spread in the memory which seems logical.