Bug 1084 – Crash (segfault) when writing unicode string on socket

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 1084 - Crash (segfault) when writing unicode string on socket

Summary:

Crash (segfault) when writing unicode string on socket

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtNetwork
Version:	1.0.8
Platform:	PC Linux

Importance:	P2 normal
Assigned To:	Paulo Alcantara

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-12-05 13:53 EET by flashcode
Modified:	2012-01-02 21:44 EET (History)
CC List:	9 users (show)

See Also:

Attachments
Script crashing on write of unicode on socket (864 bytes, text/x-python) 2011-12-05 13:53 EET, flashcode	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 flashcode 2011-12-05 13:53:40 EET

Created attachment 464 [details]
Script crashing on write of unicode on socket

Hi,

I'm using Debian Sid with Qt 4.7.3 and PySide 1.0.8.
When I write some unicode string on a socket (using write), there is a crash of
application (segmentation fault).
If I write same unicode string with PyQt4, it's working fine.

PS: I'm not sure if it's good idea to send unicode to write(), but anyway I
should be warned about problem if write does not accept unicode, and
application should not crash.

Attachment: script to reproduce crash.

Comment 1 flashcode 2011-12-05 14:03:42 EET

I forgot to mention, I have Python 2.7.2.

Comment 2 Paulo Alcantara 2011-12-15 00:04:23 EET

Hi,

I cannot reproduce this bug from the mainline.
These are the components (plus version) which I used to try to reproduce this
bug:
    - Qt version 4.7.4.
    - Python version 2.6.4
    - Apiextractor commit: 3b89c4292c26aa9ffb3abd43cd82afeb0697627a
    - Generatorrunner commit: 567ca6effaecdf97b33d1d13eada23bafe0f7535
    - Shiboken commit: c3a53de26f79a0226eb5d2d4d90c7f898d092e03
    - PySide commit: 9468253d0346c72c6bb34a9b58146252e7142490

Could you please try to reproduce this bug by using a newer version of PySide
(e.g. 1.0.9) ? Maybe a commit that has been added in PySide version 1.0.9 has
suddenly fixed this issue.

Comment 3 flashcode 2011-12-15 15:08:56 EET

Hi,

I just tested with PySide 1.0.9, which is now the version in my Debian Sid:
ii  python-pyside.qtcore     1.0.9-2  Qt 4 core module - Python bindings
ii  python-pyside.qtgui      1.0.9-2  Qt 4 GUI module - Python bindings
ii  python-pyside.qtnetwork  1.0.9-2  Qt 4 network module - Python bindings

Unfortunately, this version does not help, I still have the same crash.

Should I try with development version of PySide ? If you have nightly build for
Debian Sid (i386), it would help me to test.

PS: I tried to change version from 1.0.8 to 1.0.9 in this bug, but the version
1.0.9 is not available in list.

Comment 4 Paulo Alcantara 2011-12-17 03:40:32 EET

Hi,

Thanks for the report!

This bug has been fixed on PySide commit
86c6261dac472b623d5799a11dee6c8956daf600.