You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks, I got again the " Engine error: Invalid address in remote process" error with python 3.13
I was trying to inspect a process which got hanged while debugging with pycharm due to a threading issue. I'm not sure I'll be able to provide a MWE.
Without either a MWE or a core file, it's very unlikely that we'll be able to debug what's going wrong. "Invalid address in remote process" could mean almost anything, from a bug in PyStack to memory corruption in the process being attached to and anything in between.
Activity
dpinol commentedon Jan 28, 2026
On linux with python 3.14.2, pystack 1.6.0 fails
Engine error: Invalid address in remote process 💀godlygeek commentedon Jan 28, 2026
This should have been closed months ago; PyStack has supported 3.14 since the 1.5.0 release in August 2025.
@dpinol Please open a new issue for your problem, and provide reproduction steps.
pablogsal commentedon Jan 28, 2026
I tested with
3.14.2and it passes the test suite so there is something else at handdpinol commentedon Jan 28, 2026
thanks, I got again the " Engine error: Invalid address in remote process" error with python 3.13
I was trying to inspect a process which got hanged while debugging with pycharm due to a threading issue. I'm not sure I'll be able to provide a MWE.
godlygeek commentedon Jan 28, 2026
Without either a MWE or a core file, it's very unlikely that we'll be able to debug what's going wrong. "Invalid address in remote process" could mean almost anything, from a bug in PyStack to memory corruption in the process being attached to and anything in between.