Closed MasterCATZ closed 2 months ago
You can add a print(child.before.decode('utf-8', 'ignore'))
between line 534 and 535 in libpince/debugcore.py
because in your logs, it only shows the last 100 chars and that is not enough to tell us anything.
Also below line 323 in the same file as well.
EDIT: See Korcan's post below.
Pull the latest patch by invoking git pull
. This patch will print pexpect EOF exceptions with full child.before
data
/tmp/PINCE/-1/gdb_log.txt does not exist ?
I had run the old compile_gdb.sh before should I remove its traces ? if so how ?
I will start a fresh and try again
No need, GDB issue not PINCE. GDB crashes when you attach to the process and from what I'm seeing, it's a Proton process and GDB does not behave well with WINE programs.
I suggest using Cheat Engine for WINE stuff, PINCE is mainly designed for native Linux games.
Out of curiosity, does this happen with every Proton game you try to attach to or only this one specifically?
with linux + Steam never been able to get cheat engine to work , and neither does their ceserver even if I run CE on a windows box with the ceserver on the linux box the cheat tables never load up
oh well I will keep using game conqueror then it picks up the running process , yours calls it a GameThread
this was doing "imortals of aveum" I will see what other do
edit
thanks for leading me down the rabbit hole of getting cheatengine working I still can not get the cheat table to load but I believe its because its looking for a different exe process then what CE is seeing , but hell CE is so much faster at scanning memory the GC , now to tinker with script to look for another process as its looking for shipping in it , tho looking at the long process list CE is seeing that
PROTON_REMOTE_DEBUG_CMD="/home/aio/Downloads/CheatEngine75.exe" steam PROTON_REMOTE_DEBUG_CMD="/ZFS15k/SteamLibrary/Cheat.Engine/7.5/cheatengine-x86_64.exe" steam
%COMMAND%
Steam Tinker Launch looked like another way
You're supposed to use Cheat Engine in the same Proton prefix as the game you're running in. Search for and use wstart
which is a script that'll help you launch programs in the same prefix.
I personally use this method when I need to test CE so if it doesn't work on your end, you're doing something wrong.
Closing this issue as there's no AppImage issues and we're already tracking WINE issues here.
using PINCE-x86_64.AppImage it just crashes when attaching to a process
and will just hang their even force closing does nothing untill I pkill -9 the appimage process
/tmp/.mount_PINCE-3x0ijk/AppRun: line 8: 3927558 Killed $APPDIR/usr/bin/python3 $APPDIR/opt/PINCE/PINCE.py
and so is the version built from source
back to editing values on the fly now that I can not play with opcodes