[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
From: René Dudfield <renesd@xxxxxxxxx>
Date: Wed, 16 Sep 2009 08:50:14 +0100
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Wed, 16 Sep 2009 03:50:18 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=njGBxn/5ga7u4+n42bMh0b5RBcBLRgGkDaYZdLK/AR8=; b=TSX/y7CMwFA/chvAmOt+rfv0ch2Kled03WTm79XTVLIEFC42k/GvNLTciO87dfekx1 QN3sU/k/1EDDWjvO4/+kS9wSJ5WieJM1Tb7YaZQLTh1fG/n9bmFM3giPdTcphstbJkKh yw0dXyzg5mw/yQRZ2PvPoPWWNAQ8dt+2yF4OA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=RE93VveVOh4s/Ic3NVkwYBAB4Zwp6iZdfR1ocoQAcKDGxRb0cj9GWsYPF2YLdOyK9n Rv7psWPeV0EmaGQ9LYC9wXsO7PAhMubK7cS2HLSDq9iGCK4n2304RdsD28+O6dsT0mnR dehOAOQKJpqKhX2Y5QIgwta/21gyFnXLH8aek=
In-reply-to: <200909152356.40489.pete@xxxxxxxxxxxxxxx>
References: <200909052029.55920.pete@xxxxxxxxxxxxxxx> <200909111820.32349.pete@xxxxxxxxxxxxxxx> <64ddb72c0909111041t5cca3933y16f4ed63547d63a2@xxxxxxxxxxxxxx> <200909152356.40489.pete@xxxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

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 <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
>

Follow-Ups:
- Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
  - From: Peter Chant

References:
- [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
  - From: Peter Chant
- Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
  - From: Peter Chant
- Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
  - From: René Dudfield
- Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
  - From: Peter Chant

Prev by Author: Re: [pygame] Hexagonal collision detection?
Next by Author: Re: [pygame] PyGame Mac OS X 10.6 fail?
Previous by thread: Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
Next by thread: Re: [pygame] pygame parachute and inconsistent interned sting state - but only on Slackware 13.0 32 bit
Index(es):
- Author
- Thread