I guess the next step is to try and put print debugging in. You start by putting a few print statements in, and see where it gets up to. Then you refine until you get really close to it... doing a binary search of your source until you find the place/places that make it crash.
cheers, On Tue, Sep 15, 2009 at 11:56 PM, Peter Chant <[email protected]> wrote: > On Friday 11 September 2009, René Dudfield wrote: >> ah. that stack trace doesn't show where the problem is... looks like >> the stack is getting corrupted. > > Any thoughts on what next? My next move, in the abscence of any better plan > is to try to downgrade the version of python used in slack 13.0 to that used > in slack 12.2 - as everything works in 12.2. This does not find the bug but > it > gets me up and running. > > Pete > > > -- > Peter Chant > http://www.petezilla.co.uk >
