Bug 223 – [FTBFS] Fails to build on armel (segmentation fault)

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 223 - [FTBFS] Fails to build on armel (segmentation fault)

Summary:

[FTBFS] Fails to build on armel (segmentation fault)

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	Shiboken
Version:	0.3.2
Platform:	Other Linux

Importance:	P2 critical
Assigned To:	Marcelo Lira

URL:	https://buildd.debian.org/status/pack...

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-18 04:31 EEST by Didier Raboud
Modified:	2010-09-10 19:21 EEST (History)
CC List:	7 users (show)

See Also:

Attachments
Backtrace of the segfault on armel (3.58 KB, text/plain) 2010-06-22 06:02 EEST, Didier Raboud	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 Didier Raboud 2010-05-18 04:31:29 EEST

Hi, 

shiboken fails to build from source (FTBFS) on the following architectures:
armel; with the following error:

Segmentation fault

The complete build log is available there:

https://buildd.debian.org/build.php?pkg=shiboken&arch=armel&ver=0.3.1-1

The full Debian source package can be downloaded there :

http://packages.debian.org/source/sid/shiboken

Thanks for your help !

Cheers, 

OdyX

Comment 1 renato filho 2010-05-31 18:39:41 EEST

please could you try with git HEAD version. I created a bootstrap here and the
compilation works fine.

Comment 2 Didier Raboud 2010-05-31 18:46:28 EEST

Hi renato, 

Hrm, not really, unless if you tag a specific revision I could push to
experimental. Is a new release planned soon ?

Could the segmentation fault be related to how generatorrunner was built ?

Cheers, 

OdyX

Comment 3 Didier Raboud 2010-06-01 11:23:58 EEST

Hi, 

it failed again (which makes it failing for the third time):

https://buildd.debian.org/fetch.cgi?pkg=shiboken;ver=0.3.1-3;arch=armel;stamp=1275387443

I guess that the culprit is generatorrunner (it's the segfaulting binary
afterall), but I wonder how/why it hasn't been detected at the build-tests of
generatorrunner...

/me waits patiently on new releases. 

Cheers,

OdyX

Comment 4 Hugo Parente Lima 2010-06-01 14:05:27 EEST

If it segfaults on generatorrunner binary, the problem can be, and probably is,
at shiboken generator too. We need at least a stacktrace.

Comment 5 Didier Raboud 2010-06-11 03:17:50 EEST

Hi, 

this just happened again, when building shiboken 0.3.2. All its
build-dependencies had been built with the new "optimisation-less" build flags.

https://buildd.debian.org/fetch.cgi?pkg=shiboken&arch=armel&ver=0.3.2-1&stamp=1276227219&file=log&as=raw

I'll see if I can get a backtrace.

Cheers, 

OdyX

Comment 6 Didier Raboud 2010-06-22 06:02:35 EEST

Created attachment 49 [details]
Backtrace of the segfault on armel

Hi, 

here's a backtrace, thanks to _rene_ !

Comment 7 Didier Raboud 2010-09-02 05:17:03 EEST

Hi, this can be fixed with
http://patch-tracker.debian.org/patch/series/view/apiextractor/0.7.0-1~exp1/01_memory_alignment_fix.patch

:->

Comment 8 Hugo Parente Lima 2010-09-02 14:45:24 EEST

Patch merged into mainline
apiextractor/8bf42dccbbf969a375115bb4fa0fab223b187e8e