[Pkg-chromium-maint] Bug#680566: chromium: SIGSEGV in fopen64 at content/browser/zygote_main_linux.cc:840 on armel
shawn
shawn at jengr.tk
Fri Jul 6 19:56:01 UTC 2012
Package: chromium
Version: 20.0.1132.43~r143823-1
Severity: important
Tags: upstream
commit 71b028bc186b650b779804e04fb02650549be763
authorsergeyu at chromium.org <sergeyu at chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Redirect fopen("/dev/urandom") so that NSS can properly seed its RNG.
BUG=122169
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=131808
Review URL: https://chromiumcodereview.appspot.com/10031027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132106 0039d316-1c4b-4281-b951-d872f2087c98
introduced an insane override of fopen64() among
other syscalls.
This override segfaults on armel. Note this function has been moved to
content/zygote/zygote_main_linux.cc:769 in upstream git ( c09552b18086c31751e2547980acc41b286d5379 )
Despite the code having to do with the sandbox, using --no-sandbox
does not change the crash or backtrace.
Program received signal SIGSEGV, Segmentation fault.
0x001e4014 in ?? ()
(gdb) bt
#0 0x001e4014 in ?? ()
#1 0x2c2e0a4c in fopen64 (path=0x419294c0 "/proc/filesystems",
mode=0x419293b8 "r") at content/browser/zygote_main_linux.cc:840
#2 0x4191e624 in selinuxfs_exists ()
from /lib/arm-linux-gnueabi/libselinux.so.1
#3 0x41916f44 in ?? () from /lib/arm-linux-gnueabi/libselinux.so.1
Cannot access memory at address 0x0
#4 0x41916f44 in ?? () from /lib/arm-linux-gnueabi/libselinux.so.1
Cannot access memory at address 0x0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
To compile on armv5, I need to fix my previous skia patch ended up
wrong in this package, and also a patch to successfully use system libvpx
which I will attach to 674728
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: armel (armv5tel)
Kernel: Linux 3.4.0-tomoyo-00006-gfd64aac (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 20.0.1132.43~r143823-1
ii gconf-service 3.2.5-1
ii libasound2 1.0.25-3em1
ii libatk1.0-0 2.4.0-2
ii libbz2-1.0 1.0.6-3
ii libc6 2.13-33
ii libcairo2 1.12.2-2em1
ii libcups2 1.5.3-1
ii libdbus-1-3 1.6.0-1
ii libevent-2.0-5 2.0.19-stable-3
ii libexpat1 2.1.0-1em1
ii libflac8 1.2.1-6
ii libfontconfig1 2.9.0-6
ii libfreetype6 2.4.9-1em1
ii libgcc1 1:4.7.1-2
ii libgconf-2-4 3.2.5-1
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.10-1
ii libjpeg8 8d-1em1
ii libnspr4 2:4.9.1-1
ii libnss3-1d 2:3.13.5-1
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1em1
ii libpulse0 2.0-3
ii libspeex1 1.2~rc1-6
ii libstdc++6 4.7.1-2
ii libudev0 175-3.1em1
ii libvpx1 1.1.0-1
ii libwebp2 0.1.3-3
ii libx11-6 2:1.5.0-1
ii libxcomposite1 1:0.4.3-2
ii libxext6 2:1.3.1-2em1
ii libxfixes3 1:5.0-4
ii libxml2 2.8.0+dfsg1-4
ii libxrender1 1:0.9.7-1em1
ii libxslt1.1 1.1.26-12+rebuild1
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-6
ii zlib1g 1:1.2.7.dfsg-13
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
More information about the Pkg-chromium-maint
mailing list