Search everywhere only in this topic. Advanced Search. Classic List Threaded. Segmentation fault after call to wx. App None which I use to open a file dialog and load a set of data. The file dialog process works fine and appears to close without incident. The segmentation fault comes later in the program when I try to plot some data using pylab.
Mac OS X 10.9 Mavericks Python Segmentation fault: 11
I use the frame. Destroy command within a function that is used to open and close the file dialog, but it appears that this is persisting and causing the segmentation fault.
The code works fine on a Windows machine but fails on my Mac. Please see the attached code fragment that reproduces the problem on my Mac. I've installed python 2. In order to run this problem, I've added modules wxpython and python. I am running the problem from the command line with pythonw.
- - Nightly on Mac OSX -> Segmentation fault 11 (blows on layout)?
- virtual keyboard mac os x 10.5.
- Сбой Python при запуске двух команд (Segmentation Fault: 11).
- goodgame empire free rubies mac.
- rdp into windows machine from mac?
- set up mamp server on mac.
I suspect that the problem is that I am not using event handlers. If this is the case, I would appreciate some guidance on how to implement an event handler as I am new to python.
Duplicates of this bug
Otherwise, any advice on the problem would be most appreciated. Re: Segmentation fault after call to wx. I have not looked at your code, but seg faults are pretty common on Macs when a widget is destroyed before all delayed actions using it are complete. I have seen this oh so many times on the Mac, with code that runs fine in Linux and Windows. I use wx.
CallLater , Hope this fixes your problem. GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account. Can you check whether the python is coming from conda-forge or the default channel? A simple conda list grep python should produce the information I need just post the exact python version from that. For some reason, there's an incompatibility between the pythons supplied by conda-forge and anaconda for OSX. As also mentioned here , the error stems from the fact that pyBigWig is linked dynamically to python library, however the interpreter uses statically linked python.
So I managed to make it work with this PR. Can you try reproducing the error with this PR? See ticket comment See ticket comment - let's see how re-enabling opengl works out. The Intel driver is greylisted again in 0. Opened 4 years ago Closed 4 years ago Last modified 4 years ago. LANG : C env.
Python Segmentation fault: 11 on OSX - 程序园
SHLVL : 2 env. TERM : xtermcolor env. USER : user2 env. Oldest first Newest first Threaded.
Show comments Show property changes. I'll pass this back to you, and leave you to make a final reluctant decision.