Bug 1098 – Segmentation fault in QPalette.brush()

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 1098 - Segmentation fault in QPalette.brush()

Summary:

Segmentation fault in QPalette.brush()

Status:	RESOLVED ALREADYFIXED

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

Importance:	P1 normal
Assigned To:	Paulo Alcantara

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-12-20 15:54 EET by Catalin Drula
Modified:	2011-12-24 02:16 EET (History)
CC List:	10 users (show)

See Also:

Attachments
small program that reproduces the crash (745 bytes, text/x-python) 2011-12-20 15:54 EET, Catalin Drula	Details
backtrace from 1.0.9 (10.96 KB, text/plain) 2011-12-23 21:41 EET, anatoly techtonik	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 Catalin Drula 2011-12-20 15:54:49 EET

Created attachment 469 [details]
small program that reproduces the crash

The attached program produced a segmentation fault on PySide 1.0.8 and 1.0.9,
but NOT on PySide 1.0.2.

The stack trace shows:

Program received signal SIGSEGV, Segmentation fault.
QBrush::QBrush (this=0x1423390, other=...) at painting/qbrush.cpp:542
542    painting/qbrush.cpp: No such file or directory.
    in painting/qbrush.cpp
(gdb) bt
#0  QBrush::QBrush (this=0x1423390, other=...) at painting/qbrush.cpp:542
#1  0x00007ffff3798de9 in Shiboken::ValueTypeConverter<QBrush>::toPython
(cppobj=...) at /usr/include/shiboken/conversions.h:176
#2  0x00007ffff383f1b6 in Sbk_QPaletteFunc_brush (self=<PySide.QtGui.QPalette
at remote 0x11d7dd0>, args=<value optimized out>)
    at
/build/buildd/pyside-1.0.9/build-2.7/PySide/QtGui/PySide/QtGui/qpalette_wrapper.cpp:376

Comment 1 Hugo Parente Lima 2011-12-20 19:51:23 EET

Thanks for the report.

Comment 2 Paulo Alcantara 2011-12-23 21:11:49 EET

Hi Catalin,

I cannot reproduce this bug here. It prints out with no trouble on the screen:
"<PySide.QtGui.QBrush(QColor(ARGB 1, 0, 0, 0.501961) , SolidPattern )   at
0x1965d08>".

I've built PySide from mainline and these were the commit hashs that I built
PySide from:
    - Apiextractor: b1ec8b9ead203e552594fc21e2d54d81f6ad2915
    - Generatorrunner: 5174c6ad3818247c9586804aae2394a68ef30d47
    - Shiboken: faf9f948deb70df76a8e7f91eba861fae78e5273
    - PySide: ace1372c1a091faabdc6cfb00f187a993d31b2c4

Also the Python version used was 2.7.2. I'm guessing that you used Py2k to
reproduce that bug - that's why you used the print function without the
parentheses in-between, so I probably used the same version as you.

It would be nice if you could build PySide from mainline and try to reproduce
the same bug. Somehow I'll try any way out.

Comment 3 Hugo Parente Lima 2011-12-23 21:32:20 EET

Paulo, this bug may be fixed when setanta's branch was merged into mainline.

Comment 4 anatoly techtonik 2011-12-23 21:41:37 EET

Created attachment 471 [details]
backtrace from 1.0.9

Just reproduced on Fedora 16 with 2.7.2

I am not sure how to check hashes used to build my PySide, but it reports 1.0.9
and the hashed should be the ones from BuildScripts repository for this
version.

Comment 5 Paulo Alcantara 2011-12-23 22:12:02 EET

(In reply to comment #3)
> Paulo, this bug may be fixed when setanta's branch was merged into mainline.

Indeed.

(In reply to comment #4)
> Created attachment 471 [details]
> backtrace from 1.0.9
> 
> Just reproduced on Fedora 16 with 2.7.2
> 
> I am not sure how to check hashes used to build my PySide, but it reports 1.0.9
> and the hashed should be the ones from BuildScripts repository for this
> version.

As Hugo said, this bug might be fixed once setanta's branch was merged into
mainline. Those changes made by setanta's branch will only be available on the
next version of PySide. Ocasionally you might want to build PySide from
mainline by retrieving the source files for the Apiextractor, Generatorrunner,
Shiboken and PySide at http://github/PySide and then build and install each
one.

Comment 6 anatoly techtonik 2011-12-24 00:22:33 EET

It is much easier to use https://github.com/PySide/BuildScripts for building
and using latest PySide.

Comment 7 anatoly techtonik 2011-12-24 01:21:42 EET

Example works ok with HEAD.

Comment 8 Paulo Alcantara 2011-12-24 02:16:24 EET

Hi Anatoly,

(In reply to comment #7)
> Example works ok with HEAD.

That's great! :-)

Closing this bug and marking as RESOLVED (ALREADYFIXED).