[Pkg-chromium-maint] Bug#680566: chromium: SIGSEGV in fopen64 at content/browser/zygote_main_linux.cc:840 on armel

[shawn]

On Fri, 2012-07-06 at 17:04 -0500, Jonathan Nieder wrote: 
> shawn wrote:
> 
> >> Any idea what the cause is?  E.g., can you find where in the function it
> >> crashes by judicious use of printf, do you know what is on line 840 in
> >> the source of the binary you are testing, or can you get gdb to print
> >> which part of the assembly 0x2c2e0a4c refers to?
> >
> > Dump of assembler code for function fopen64(char const*, char const*):
> >    0x022e09d4 <+0>: push {r4, r5, lr}
> [...]
> 
> Maybe ASLR has caused a different address to be used here. :(

oh yeah didn't notice that its a totally differn't address. but aftera
reload i get the crash at the same place

(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?)
(gdb) dissasemble x2c2e0a4c
Undefined command: "dissasemble".  Try "help".
(gdb)  disassemble x2c2e0a4c
No symbol "x2c2e0a4c" in current context.



-- 
-Shawn Landden