I can confim that using bfd instead of gold fixes the issue on armhf.
armel seems to be sufering from the same issue but I have not yet tried
a build with bfd on armel.
I will do an armel (but on armv7 hardware, I don't have any armv4t or
armv5 hardware to test on and all my armv6 stuff is running raspbian)
build and test once I have finished doing the one for raspbian,
unfortunately each build takes days on my imx53 (I have an odriod u2 on
order which should speed things up)
Patch to make the package use bfd rather than gold on armel and armhf is
attached. I may or may not upload this as a NMU.
diff -Nru chromium-browser-22.0.1229.94~r161065+dfsg/debian/changelog
chromium-browser-22.0.1229.94~r161065+dfsg/debian/changelog
--- chromium-browser-22.0.1229.94~r161065+dfsg/debian/changelog 2012-12-31
20:02:00.000000000 +0000
+++ chromium-browser-22.0.1229.94~r161065+dfsg/debian/changelog 2013-01-05
12:54:20.000000000 +0000
@@ -1,3 +1,10 @@
+chromium-browser (22.0.1229.94~r161065+dfsg-0.2) unstable; urgency=low
+
+ * Change build-depends/build-conflicts to avoid gold linker on arm* as it
+ seems to be causing segfaults (Closes: 696909)
+
+ -- Peter Michael Green <plugw...@debian.org> Sat, 05 Jan 2013 12:52:12 +0000
+
chromium-browser (22.0.1229.94~r161065+dfsg-0.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru chromium-browser-22.0.1229.94~r161065+dfsg/debian/control
chromium-browser-22.0.1229.94~r161065+dfsg/debian/control
--- chromium-browser-22.0.1229.94~r161065+dfsg/debian/control 2012-10-17
23:19:01.000000000 +0000
+++ chromium-browser-22.0.1229.94~r161065+dfsg/debian/control 2013-01-05
12:56:07.000000000 +0000
@@ -63,7 +63,7 @@
libxt-dev,
libxtst-dev,
libpam0g-dev,
- binutils-gold,
+ binutils-gold [!armel !armhf],
libflac-dev,
libwebp-dev,
autotools-dev,
@@ -80,6 +80,8 @@
subversion,
libudev-dev,
libssl-dev
+Build-Conflicts:
+ binutils-gold [armel armhf]
Standards-Version: 3.9.2
Package: chromium-browser
