Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit

[Peter Chant <pete@xxxxxxxxxxxxxxx>]

On Wednesday 16 September 2009, René Dudfield wrote:
> 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.
>

D'oh so obvious.  What I regularly do whilst developing things, but not when 
bugs suddenly appear.

FOUND IT!
     self.screen.blit(clear,(0,0))


 - look for the exclamation marks

    def clearScreen(self):
	print "In clearScreen"
        print "About to call pygame.display_get_surface()"
        clear = pygame.display.get_surface()
        print "About to fill surface to clear it"
        clear.fill((0,0,0))
        print "About to self.screen.blit - !!!! this crashes"
        self.screen.blit(clear,(0,0))
        print "just blitted - !!!!! does not get to here"


self.screen is initialised by the output of another class.
  self.screen = h.screen

in class h 

  self.screen=pygame.display.get_surface()


Only fails on 32 bit Slack 13.0.



>
> cheers,
>
> On Tue, Sep 15, 2009 at 11:56 PM, Peter Chant <pete@xxxxxxxxxxxxxxx> 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


-- 
Peter Chant
http://www.petezilla.co.uk