Bug 187 – On Maemo x86 Scratchbox, qtcore_qflags test segfaults

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 187 - On Maemo x86 Scratchbox, qtcore_qflags test segfaults

Summary:

On Maemo x86 Scratchbox, qtcore_qflags test segfaults

Status:	CLOSED FIXED

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

Importance:	P5 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-03-19 16:28 EET by Matti Airas
Modified:	2010-04-07 11:18 EEST (History)
CC List:	7 users (show)

See Also:

Attachments
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-03-19 16:28:52 EET

The current PySide Shiboken tools and bindings build just fine on Maemo x86
Scratchbox. I ran the tests without having the X11 server setup in place, and
qtcore_qflags segfaults:

[sbox-FREMANTLE_X86: ~/pyside/pyside-shiboken/build] > ctest -R qtcore_qflags
-V
UpdateCTestConfiguration  from
:/home/matairas/pyside/pyside-shiboken/build/DartConfiguration.tcl
Start processing tests
UpdateCTestConfiguration  from
:/home/matairas/pyside/pyside-shiboken/build/DartConfiguration.tcl
Test project /home/matairas/pyside/pyside-shiboken/build
Constructing a list of tests
Done constructing a list of tests
Changing directory into /home/matairas/pyside/pyside-shiboken/build/tests
 11/153 Testing qtcore_qflags                 
Test command: /scratchbox/tools/bin/sh
/home/matairas/pyside/pyside-shiboken/tests/run_test.sh 
/home/matairas/pyside/pyside-shiboken/build:/home/matairas/pyside/pyside-shiboken/tests/util
/targets/FREMANTLE_X86/usr/bin/python2.5
/home/matairas/pyside/pyside-shiboken/tests/qtcore//qflags_test.py
Test timeout computed to be: 5
..../home/matairas/pyside/pyside-shiboken/tests/run_test.sh: line 13: 21077
Segmentation fault      (core dumped) $3 $4
-- Process completed
***Failed 

0% tests passed, 1 tests failed out of 1

The following tests FAILED:
     11 - qtcore_qflags (Failed)
Errors while running CTest



Furthermore, when trying to debug the issue, also gdb segfaults:

[sbox-FREMANTLE_X86: ~/pyside/pyside-shiboken/build] > gdb --args python2.5
../tests/qtcore/qflags_test.py 
GNU gdb (GDB) 6.8.50.20090417
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(no debugging symbols found)
(gdb) r
Starting program: /targets/FREMANTLE_X86/usr/bin/python2.5
../tests/qtcore/qflags_test.py
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
free(): invalid pointer 0x956006f!
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Segmentation fault (core dumped)

Comment 1 Anderson Lizardo 2010-03-19 17:29:55 EET

To make gdb not segfault inside stratchbox, you should install the
"maemo-debug-scripts" package and run "gdb-native" instead.

At least works for me in such cases.

Comment 2 Hugo Parente Lima 2010-04-07 11:17:26 EEST

Fixed in commit shiboken/a38c294732542b8d25ca1a34856c2ffa4fa2b1ac

Comment 3 Hugo Parente Lima 2010-04-07 11:18:28 EEST

shiboken version 0.2.0 comes with this fix.