mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: getrlimit failed (chromium on musl)
Date: Sat, 28 Jan 2017 14:14:07 +0100	[thread overview]
Message-ID: <20170128131406.GS17692@port70.net> (raw)
In-Reply-To: <CAPG2z0_Vgo94xkO_6eVXGcMxHmmC6Da614gcJUKXh=JL743+qQ@mail.gmail.com>

* He X <xw897002528@gmail.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.



  reply	other threads:[~2017-01-28 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 14:08 Alba Pompeo
2017-01-18 14:18 ` Rich Felker
2017-01-18 15:18   ` Alba Pompeo
2017-01-18 15:56     ` Rich Felker
2017-01-18 15:51 ` Samuel Holland
2017-01-18 16:13   ` Alba Pompeo
2017-01-27  0:41     ` Alba Pompeo
2017-01-28  6:00       ` He X
2017-01-28 13:14         ` Szabolcs Nagy [this message]
2017-01-28 19:45         ` Samuel Holland
2017-01-28 20:59           ` Rich Felker
2017-01-29  4:54             ` He X
2017-01-29 23:13       ` Samuel Holland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170128131406.GS17692@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).