2010/12/24 Thomas Perl <[email protected]>: > Hi, > > 2010/12/24 Bruno Araujo <[email protected]>: >>> I got a segfault with the new Pyside binding 1.0.0b2 where i didn't >>> get with beta1. How can i found such segfault without adding print >>> everywhere in the code ? >>> Pdb segfault too. >> >> Run you script with '-m trace --trace' params, it should point which >> line is causing the segfault. Supposing your programs is named >> script.py, one way to do it is: >> >> $ python -m trace --trace script.py > > Can we have that info on the PySide Wiki? I think it might be useful > for other developers who run into such problems to have a known way on > how to best file a segfault and what information should be provided in > the bug report.
Ok, I can put this bit of info on the wiki, just let me find a proper place to it. -- ____________________________________ Bruno Araújo Software developer - openBossa Labs - INdT _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
