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

Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
From: "Brian Fisher" <brian@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 7 Jun 2008 14:46:49 -0700
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Sat, 07 Jun 2008 17:46:53 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=eK14imXzacxQVYiOSvUUTCo2NDNaH5gdMd1Bn+dqRxY=; b=dGjphju1VaPuAVBJtiiV/3N2PIdLKq7Qq2MhlzwTHmL3SZ7onBbTUOKLgxbAVgcZPF o4iDPp0oWCfQ8gnB2wWqD8M8HqOW9tl4k7w3u8q3h4KX9dehDvFTTLtinSVl2ltjbDsh 2LWHxobfQUEdaKhkJGv7wHvsIVS+xixkH2h+o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=JEtilvEtc9nyyLazeH3IH+Pv+a9t2QWTcoDVUo0XW+40YKfMSkwb+GyApuXOC5wBoJ G0wFYctxnRbqdq51TOapOoPaQeaIBnuuaC6xwzYJINed0HMwoCazuXMAS29TZI6LeFvz w+ciu1lUY6zxdDY410JS6BhrQ2DjZX2KyVSXg=
In-reply-to: <20080607201920.GA1148@xxxxxxxxxxxxxxxxxxx>
References: <dc44bb3e0806061220u7baa77ebma5910edc90f50c9b@xxxxxxxxxxxxxx> <e55f7e400806062136j14f2f56le7d1727046ffd22@xxxxxxxxxxxxxx> <dc44bb3e0806070912g17f6c20xd1728d5109f46d33@xxxxxxxxxxxxxx> <20080607201920.GA1148@xxxxxxxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

On Sat, Jun 7, 2008 at 1:19 PM, Marcus von Appen <mva@xxxxxxxxxxxx> wrote:

After this manual unlock, the PixelArray is unlikely to work in any
case. You might expect weird behaviour in some cases, random
segmentation faults and other crashes on trying to access self.pixels
after the unlock. See my other mail about the why and how to avoid such
things.

would it be good to try and turn that into an exception? like if the PixelArray would check the lock count or something?

Follow-Ups:
- Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
  - From: Marcus von Appen

References:
- [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
  - From: Jake b
- Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
  - From: Brian Fisher
- Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
  - From: Jake b
- Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
  - From: Marcus von Appen

Prev by Author: Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
Next by Author: Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
Previous by thread: Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
Next by thread: Re: [pygame] no unlock: surfarray.pixels2d() and PixelArray() bug or intented?
Index(es):
- Author
- Thread