Alex

@sffool could you attach a sample .pyc with that opcode?

@zrax OK, but usually having pyc you could a) have some sample to play with b) create a test case in Python (after reading/understanding provided .pyc) and thus close the...

> Please support: JUMP-BACKWARD possible solution https://github.com/zrax/pycdc/pull/472

Please attach your .pyc

This is logical flow issue The only way IMHO is to debug it by step-by-step tracing over opcode handlers and analyzing stack history/etc

I see that official supported last version is python 3.11  so the question about running tool on 3.12 is actual

tried same sample above on Python 3.12: ``` Warning: Stack history is not empty! Warning: block stack is not empty! a = { '123': '456' } b = { }...

some clues might be over here https://github.com/python/cpython/issues/51444

Regarding >Navigate to _MAPNAV_NEW function in Exports there is no such API, did you mean _MAPNAV_MNEW ? 

the freshly baked version 11.0 still has this bug: