unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: raingloom <raingloom@riseup.net>
Cc: 43610@debbugs.gnu.org
Subject: bug#43610: IceCat segfault
Date: Sun, 27 Sep 2020 16:36:52 -0400	[thread overview]
Message-ID: <87v9fz6jnk.fsf@netris.org> (raw)
In-Reply-To: <20200927074937.3b23c327@riseup.net>

Hi,

raingloom <raingloom@riseup.net> writes:

> On Sat, 26 Sep 2020 14:05:53 -0400
> Mark H Weaver <mhw@netris.org> wrote:
>
>> In the meantime, to start IceCat 78 with your existing profile but
>> with addons temporarily disabled, try running:
>> 
>>   icecat -safe-mode
>> 
>> That should allow you to recover your existing bookmarks, history,
>> cookies, saved passwords, tabs, etc.  Then you can try adding back
>> your preferred addons incrementally to find out which one is causing
>> the problem.
>
> It still crashes with the -safe-mode flag. Luckily I keep most things
> outside modern browsers, so it's not a huge loss. (For obvious reasons
> I do not consider them reliable.)

If you'd like to try another experiment, it would be interesting to know
if you're able to recover most of your old profile by running "icecat
-safe-mode -p", selecting your old profile, and clicking on the "Refresh
IceCat" button that is presented.  That will reset all preferences to
the IceCat defaults, but might enable you to recover the things I listed
above.

>> > Tbh this would be a good time to have a debug output for IceCat on
>> > hand.  
>> 
>> While I acknowledge that it might occasionally be useful in edge cases
>> like this, it would also dramatically increase the memory requirements
>> at build time. [...]
>
> Huh, I was not aware that it increased build time memory requirements.
> I assumed it just gets sent to the void in the 'strip phase, just like
> it is in other packages.

We currently pass "--disable-debug" and "--disable-debug-symbols" to
IceCat's configure script, which causes it to pass compiler flags that
disable generation of debug symbols during the build.

> As a fellow 4 gigger/thinkpadder I
> appreciate anything that lets me build things locally without 16+ gigs
> of swap. (you might think that's an exaggeration, but then you haven't
> tried to build Idris 2 with Idris 1.)

I've actually tried (and failed) to build Idris 1 locally, so I can
sympathize :-/

       Mark




  reply	other threads:[~2020-09-27 20:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 13:26 bug#43610: IceCat segfault raingloom
2020-09-25 16:11 ` Mark H Weaver
2020-09-26  2:34   ` raingloom
2020-09-26 18:05     ` Mark H Weaver
2020-09-27  5:49       ` raingloom
2020-09-27 20:36         ` Mark H Weaver [this message]
2020-10-01 22:57           ` raingloom
2020-10-01 23:28             ` raingloom
2020-10-09  7:42               ` Ricardo Wurmus
2020-11-30 20:06                 ` Ricardo Wurmus
2020-11-30 20:12                   ` Ricardo Wurmus
2020-12-13 18:19               ` Alex ter Weele
2020-12-15 11:24                 ` Ludovic Courtès
2022-07-11 18:38                   ` Maxim Cournoyer
2020-10-01  1:56       ` Mike Gerwitz
2023-04-07 16:14 ` bug#43610: Segfault still an issue Dominik Delgado via Bug reports for GNU Guix
2023-04-08  7:55 ` Dominik Delgado via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87v9fz6jnk.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=43610@debbugs.gnu.org \
    --cc=raingloom@riseup.net \
    /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.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).