Bug 338 – Program segfaults (or behaves unexpectedly) when QGraphicsItem.itemChange is defined

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 338 - Program segfaults (or behaves unexpectedly) when QGraphicsItem.itemChange is defined

Summary:

Program segfaults (or behaves unexpectedly) when QGraphicsItem.itemChange is ...

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtGui
Version:	HEAD
Platform:	All All

Importance:	P5 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-09-02 08:20 EEST by Matti Airas
Modified:	2010-09-10 19:22 EEST (History)
CC List:	8 users (show)

See Also:

Attachments
Testcase (474 bytes, text/x-python) 2010-09-02 08:20 EEST, Matti Airas	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matti Airas 2010-09-02 08:20:28 EEST

Created attachment 78 [details]
Testcase

This took some time to find out:

When a class inheriting from QGraphicsItem has the itemChange method defined,
the PySide program segfaults or behaves otherwise unexpectedly when
QGraphicsScene.addItem is called.

This affects the diagramscene.py example, which simply doesn't get any items
added. The attached example segfaults instead. If itemChange is commented away,
everything works. The example also works on PyQt.

Comment 1 renato filho 2010-09-09 15:28:11 EEST

fixed on commit PySide:

commit ae435c55fc8bdc6b2c6456e0f4d00589d7b3bb2c
Author: Renato Filho <renato.filho@openbossa.org>
Date:   Thu Sep 9 15:24:51 2010 -0300