-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pycdc error #486
Comments
those are different apps |
I was also getting consistent segmentation faults when trying to decompile python 3.10 and 3.11. it's not surprising considering it's not fully if not at all supported yet. Afair it was segfaulting trying to dereference an empty stack. Regardless, the decompiled code would be false even if the invalid access was protected by a check, since I'm pretty sure op was also trying to decompile python 3.9+ |
I also get segmentation fault if I run the tests. However, these issues only occur for the Release build - in particular, turning on any optimization (i.e. at least -O1), results in segmentation fault with the checks:
|
Very interesting! what Linux distro do you run? |
This problem first occurred when I was porting the software to FreeBSD (compilation with clang/clang++), and I reproduced the issue on Slackware 15 (fresh install from ISO). I can check if the same issue occurs on Devuan... |
OK, just checked it now - problem also happens in Devuan 5.0.1
FreeBSD: python version 3.9.19 Forgot to mention explicitly, if I turn optimization to -O0, and run the checks, all is fine! |
Thanks for details! but release build (even wihtout -O2 flag did crash a couple of times with coredumps! I'm using FreeBSD 14.1 BTW, the default shell in above OS is /bin/sh and it is not possible to run the tests, @zrax is it OK to make shebang more generic and cover majoriyt of OSes? #!/bin/bash here is a small PR if you agree |
pycdc error(segmentation fault) but pycdas bytecode decompile successfully. why??
The text was updated successfully, but these errors were encountered: