Bug 651 – Calling disconnect() with no arguments causes segfault

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 651 - Calling disconnect() with no arguments causes segfault

Summary:

Calling disconnect() with no arguments causes segfault

Status:	CLOSED FIXED

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

Importance:	P2 major
Assigned To:	Hugo Parente Lima

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-01-27 19:27 EET by Evan Patterson
Modified:	2011-02-02 15:46 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Test case (232 bytes, text/x-python) 2011-02-01 15:38 EET, Evan Patterson	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 Evan Patterson 2011-01-27 19:27:25 EET

When disconnect() is called on a signal with no arguments (i.e., with the aim
to disconnect all slots), the application segfaults. This bug seems to affect
all signals, although I have only tried a few signals on QPlainTextEdit and
QAbstractTextDocumentLayout.

Comment 1 Matti Airas 2011-01-28 09:56:16 EET

Thanks, prioritizing P2.

Could you provide a minimal test case for the issue?

Comment 2 Evan Patterson 2011-02-01 15:38:20 EET

Created attachment 244 [details]
Test case

A small test case that works with PyQt4 but segfaults with PySide.

Comment 3 Hugo Parente Lima 2011-02-02 11:45:11 EET

Fixed in commit:

pyside/3270dde028cbcf23e7ea1ed468f06e0f01965538

Comment 4 renato filho 2011-02-02 15:46:13 EET

released on beta 5