Brian,
That’s already done. I work at a console prompt so that’s where I prefer to see messages. The only output I get is the diagnostics from the various print statements I put in the code to track down the problem.
No trace back, no nothing until I get the segmentation fault printed on the screen.
···
On Thu, Jul 17, 2008 at 7:20 AM, brian.d.fett@seagate.com wrote:
I would start to track this down by
disabling the stout forwarding:app = wx.App(redirect=False)
If you create your wx.App with argument
False, then the stout information is kept in the calling program (be it
drPython, or X) rather than sent to a GUI window. Very useful for fixing
bugs that cause crashes.I am not sure if this is what you needed,
but this is how I would start to “go about tracking
this down.”-Brian
Brian Fett
1280 Disc Dr
SHK224
Shakopee, MN 55379
Phone: (952)402-2595
“Timothy Grant”
timothy.grant@gmail.com
Sent by: wxpython-users-bounces@lists.wxwidgets.org
No Phone Info Available
07/16/2008 04:33 PM
Please respond to
To
Subject
[wxpython-users] My app crashes on Windows,
but not on OSX.
Up until today, the code I have written on my PowerBook
has performed flawlessly on Windows too. I don’t have a windows box to
test on, so rely on a friend who has a Vista box.My most recent iteration of code works just fine for me, but when he gets
it he can make it crash, a hard crash, no traceback no anything, and I
have no idea where to start debugging this process.I’m using a Notebook and have some widgets on Tab 1, that affect the content
of Tab 2. The crash occurs when clicking on Tab 2.Does anyone have any ideas on how I should go about tracking this down?
–
Stand Fast,
wxpython-users mailing list
tjg. [Timothy Grant]
_______________________________________________
wxpython-users mailing list
–
Stand Fast,
tjg. [Timothy Grant]