Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Request] Firefox didn't have crash detection (about:crashes does not exist), possibly because Mozilla Crash Reporter is not included in the installer ? 
Date: Tue, 30 Mar 2021 16:01:15 +0200	[thread overview]
Message-ID: <20210330140115.Rf2bHrOWWA8R3oeU_aYasEmquW_pu11z71aUO99Nlkc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29872@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29872#issuecomment-810279699

Comment:
I believe Firefox does a weird dance where it catches at least SIGSEV, does something about it, and then signals all threads with SIGSEV again. That might make some core dumps weird.

Given that using core dumps is more involved, I would assume having a way to send crash reports directly to Mozilla is interesting, as long as it actually works with our stripped packages. We'd have to check that.

  parent reply	other threads:[~2021-03-30 14:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  6:10 [ISSUE] " thegarlynch
2021-03-30 12:14 ` ericonr
2021-03-30 13:38 ` thegarlynch
2021-03-30 13:40 ` thegarlynch
2021-03-30 13:40 ` thegarlynch
2021-03-30 13:41 ` thegarlynch
2021-03-30 13:47 ` Duncaen
2021-03-30 13:48 ` Duncaen
2021-03-30 14:01 ` ericonr [this message]
2021-03-30 14:19 ` Duncaen
2021-03-30 14:21 ` Duncaen
2021-03-30 14:47 ` ericonr
2021-03-31  1:30 ` [ISSUE] [CLOSED] " thegarlynch

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=20210330140115.Rf2bHrOWWA8R3oeU_aYasEmquW_pu11z71aUO99Nlkc@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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).