-
Notifications
You must be signed in to change notification settings - Fork 15
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
Segmentation fault: 11 #78
Comments
Unfortunately I don't think any of us have macs to test with. We can still try to debug it though. Can you try running the proxy without any plugins installed? If it works, add the plugins back one by one to see if we can narrow it down. If the proxy doesn't work without plugins, does the upstream repo work? https://github.com/kakaroto/SWProxy/releases/latest |
I downloaded the upstream and tried to run Just to make sure, I even commented L8 After re-reading the call stack, it was crashing on I have latest pyqt ( Should I report that to upstream or is that something you guys look into to? (since I guess we think GUI is a plugin) |
Okay, so after second thoughts, I tried:
Which is ok, but then I thought about dependencies, so I did
Checking brew's Homebrew/homebrew-core#1705 showed this: I installed the other brew formula, Do you know how to make the changes in order to test on pyqt5? If works, maybe would be good to use https://github.com/spyder-ide/qtpy in order to use pyqt5 on sierra and qt4 on lower (and other systems), or just entirely move to qt5 :P |
Hi there,
Last time I used SWProxy was the
.100
one on Yosemite, I believe two months ago. After I upgraded to Sierra this month, trying to run SWProxy ends onSegmentation fault: 11
, even though I didn't touch the folder.I downloaded the
.102b
, ranpython setup.py install
and still same thing when runningpython SWProxy.py
:I also get the following error window:
Reinstalling Python (v2.7.13, with
brew reinstall python
) and reinstalling deps (sudo -H easy_install pycrypto dpkt yapsy
) didn't work either. Google search just pointed me to 10.9.X issues on python, which is not applicable to 10.12.XSo it's something on the code which looks incompatible with Sierra. Any ideas what could it be?
Thanks.
The text was updated successfully, but these errors were encountered: