Bug 222 – Bus error makes shiboken sparc build fail

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 222 - Bus error makes shiboken sparc build fail

Summary:

Bus error makes shiboken sparc build fail

Status:	CLOSED FIXED

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

Importance:	P2 critical
Assigned To:	renato filho

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 for shiboken SIGBUS (4.14 KB, text/plain) 2010-06-18 06:50 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:23 EEST

Hi, 

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

Bus error

The complete build log is available there:

https://buildd.debian.org/build.php?pkg=shiboken&arch=sparc&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 Didier Raboud 2010-06-11 03:20:33 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=sparc&ver=0.3.2-1&stamp=1276208449&file=log&as=raw

I'll see if I can get some help about that.

Cheers, 

OdyX

Comment 2 Didier Raboud 2010-06-18 06:50:25 EEST

Created attachment 48 [details]
backtrace for shiboken SIGBUS

Hi, 

I could get tumbleweed get me a backtrace for that failure. Thanks to him !

Cheers, 

OdyX

Comment 3 Didier Raboud 2010-07-29 14:45:56 EEST

Hi, 

this bug is now a bigger problem for Debian: it won "RC" severity level
(http://bugs.debian.org/590302 ). I am really willing to fix it, but it's hard,
because it only appears when compiling shiboken, so it takes time to test.

Could you please create a test within apiextractor that would test this bug in
particular ? With that, it would be really easier to also find people with
access, willing to help. Thanks in advance, cheers, 

OdyX

Comment 4 Didier Raboud 2010-07-29 14:54:12 EEST

Re-asssigning as the problem is in apiextractor and not in shiboken.

See the Debian bug log for details.

Comment 5 Didier Raboud 2010-08-08 12:50:17 EEST

Aye. I could test 0.7.0 in a sparc machine and it failed again. Tagging as HEAD
for now. I have a network access to said machine, please coordinate the
bugsquasing with me over IRC.

Comment 6 Didier Raboud 2010-08-08 13:20:41 EEST

Hmm. Test-building with that patch right now: 

http://patch-tracker.debian.org/patch/series/view/qtscriptgenerator/0.1.0-3/general/memory_alignment_fix.diff

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

Hi. This works with the following patch:
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 10:41:02 EEST

I'll test the patch on x86, x86_64 and arm them create a merge request.

Comment 9 Hugo Parente Lima 2010-09-02 14:44:56 EEST

Patch merged into mainline.
apiextractor/8bf42dccbbf969a375115bb4fa0fab223b187e8e