[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170128131406.GS17692@port70.net>
Date: Sat, 28 Jan 2017 14:14:07 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: getrlimit failed (chromium on musl)
* He X <xw897002528@...il.com> [2017-01-28 14:00:59 +0800]:
> After patched, chromium segfault three times in two days, e.g. when i try
> to upload a file in a baiduyun, crash when i click the upload button, and
> suddenly crashed twice, when --disable-sandbox, no crashing:
> [65422.256448] chromium[12257]: segfault at 3c1 ip 00007f69e30e075c sp
> 00007ffe5442efc0 error 4 in libc.so[7f69e30b9000+a1000]
>
can you provide your libc.so binary?
or at least objdump around address
0x00007f69e30e075c - 0x7f69e30b9000 = 0x2775c
objdump -rdw libc.so |grep -C 100 '2775c:'
make the context (-C) large enough so we see the function
entry, a proper backtrace would be useful too (e.g.
looking at the coredump from gdb).
> This patch is a bit dangerous, though it indeed solved the problem, i think
> EPERM is needed. Modifying musl is a better way, but is that correct?
disabling syscalls with EPERM is a chrome bug,
but this issue seems independent.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
