in reply to Debugging Win32::GUI Crashes

Take a look in the Event log->application view, it may provide some extra information. You could configure DrWatson to produce a crash dump, if you have the will to try and understand such.

Otherwise, it's a case of commenting stuff out until it stops crashing, then putting it back a piece at a time until it does it again. That should localise the problem enough that you can what your doign wrong.


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon