Bug 559 – Segfault on signal emit() with user defined class

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 559 - Segfault on signal emit() with user defined class

Summary:

Segfault on signal emit() with user defined class

Status:	CLOSED WORKSFORME

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	HEAD
Platform:	PC Linux

Importance:	P2 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-12-21 09:50 EET by Piotr Sokołowski
Modified:	2011-01-06 16:25 EET (History)
CC List:	10 users (show)

See Also:

Attachments
Test file (349 bytes, text/x-python) 2010-12-21 09:58 EET, Piotr Sokołowski	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 Piotr Sokołowski 2010-12-21 09:50:20 EET

Comment 1 Piotr Sokołowski 2010-12-21 09:57:26 EET

Test code works with 1.0.0 beta1 version, so it's look like regression.

When using user defined classes in signals, program ends with segfault. 
I'm aware of http://developer.qt.nokia.com/wiki/Signals_and_Slots_in_PySide and
especially "Python types and C types can be passed as parameters to it" part of
signal description, but it's not specify if it's "Python types" or "Python
built-in types". Also I wasn't able to find any PySide documentation covering
whole QtCore.Signal topic. 
Anyway, on version from 27.11.2010 test program works fine.

Comment 2 Piotr Sokołowski 2010-12-21 09:58:16 EET

Created attachment 199 [details]
Test file

Comment 3 Matti Airas 2010-12-21 10:20:37 EET

OK, thanks for the bug. Nasty that we still keep getting regressions - I'm
prioritizing this P2 to have it (most likely) fixed during the current sprint
(before Jan 07).

Could you please file a separate bug(s) about the documentation issues,
specifying in a bit more detailed manner what kinds of improvements you'd
prefer to have.

Comment 4 Benoît HERVIER 2010-12-27 03:33:18 EET

*** Bug 571 has been marked as a duplicate of this bug. ***

Comment 5 Hugo Parente Lima 2010-12-30 15:37:59 EET

Works for me with current git HEAD, maybe it was just a transient problem.

Would you check if the problem still existing for you? If it still valid, just
reopen the bug and we will do a more deep investigation.

Comment 6 Benoît HERVIER 2010-12-30 16:57:52 EET

Indeed works for me too with current git head with Qt 4.6.3 and Python2.6 on
Debian. Didn't test on Maemo as i didn't have scratchbox installed.

Comment 7 Piotr Sokołowski 2010-12-31 05:05:02 EET

Yes it's looks like transient problem, because now it's working fine.

Comment 8 renato filho 2011-01-06 16:25:24 EET

released on beta3