Hello friends,
I have a program that is behaving badly, and I’m trying to figure out an easier way to solve it. I’m using Python 2.7.10 with wxPython 3.0.2.0. On Linux (Arch and Debian at least, I’ve heard that some distros don’t display these warnings), we are getting massive amounts of spam to the console when the program starts, and evem more so as the program runs, see here: https://gist.github.com/DarkFenX/e5b5f16a6407425e403b
This does not happen when we use wxPython 2.8.12.1 via wxversion.select().
I have been reading up on it, and information regarding it seems to be slim. Most folks point to using gdb to figure out where in the Python code the warnings are coming up. The issue is that I am not familiar with this program, and I have not yet been able to utilize it. I am hoping someone can give me a quick how to to running a python script through this to pinpoint where in the python source these errors are coming from.
I have already compiled python2, wxPython 3, and wxgtk with debugging symbols. The part that I am getting stuck on is actually running it through where the GTK warnings will cause fatal errors. People say to use --g-fatal-warnings, but I’m not sure where to put this. I’ve tried putting it at the end of my script as an argument, but with no luck (understandably, as my script doesn’t know what to do with it).
If anybody needs the source for the program to verify or collect more information, here is a link to the current wx3 branch archive: https://github.com/DarkFenX/Pyfa/archive/wx3.zip The script you want to run is pyfa.py with python2 and wxPython 3 (again, we’re using 3.0.2.0)
I have spent the past three days trying to get debugging to work so that it will pinpoint the source of these issues. In the meantime, I have been having to litter sys.exit() around to try to find the next warning and narrow it down from there, but I would like a much more efficient way with gdb.
Thanks for any help