unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve Lorimer <steve.lorimer@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41240@debbugs.gnu.org
Subject: bug#41240: 26.3; crash on startup when running package-refresh-contents
Date: Wed, 13 May 2020 14:00:53 -0500	[thread overview]
Message-ID: <CAE-NPOh-5M0ATk4i28par0D=ojaMRr2uF1WXqNBnrZNGwuBHtg@mail.gmail.com> (raw)
In-Reply-To: <83tv0j66wr.fsf@gnu.org>

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

Thanks Eli.

I built 26.3 from source and it no longer crashes - must be an issue with
the snap - in fact, I've found a related issue here:
https://github.com/alexmurray/emacs-snap/issues/12

Thanks
Steve

On Wed, 13 May 2020 at 13:12, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Steve Lorimer <steve.lorimer@gmail.com>
> > Date: Wed, 13 May 2020 12:41:49 -0500
> >
> > I am running emacs 26.3 on ubuntu 20.04, installed via snap from [
> scapcraft.io/emacs]
> > (https://snapcraft.io/emacs), the `latest/stable 26.3` snap.
> >
> >     $ emacs --version
> >     GNU Emacs 26.3
> >     ...
> >
> > I have distilled my `init.el` file down to the following bare minimum:
> >
> >     (require 'package)
> >     (setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")))
>
> >     (package-initialize)
> >     (package-refresh-contents)
> >
> > Starting emacs with this `init.el` file results in a crash
> >
> >     Fatal error 11: Segmentation fault
> >     Backtrace:
> >     /snap/emacs/296/usr/bin/emacs[0x58f0c7]
> >     ...
> >
> > Loading the core file in gdb I get the following stack trace:
> >
> >     #0  0x00007f8ce2e65727 in raise () from
> /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0
> >     #1  0x0000000000567d08 in terminate_due_to_signal ()
> >     #2  0x000000000058e802 in handle_fatal_signal ()
> >     #3  0x000000000058e7d3 in deliver_thread_signal ()
> >     #4  0x000000000058e83d in deliver_fatal_thread_signal ()
> >     #5  0x000000000058e9f9 in handle_sigsegv ()
> >     #6  <signal handler called>
> >     #7  0x00007f8ce9cbeac8 in ?? () from
> /snap/core18/current/lib64/ld-linux-x86-64.so.2
> >     #8  0x00007f8ce9cc70bd in ?? () from
> /snap/core18/current/lib64/ld-linux-x86-64.so.2
> >     #9  0x00007f8ce22c92df in _dl_catch_exception () from
> > /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #10 0x00007f8ce9cc67ca in ?? () from
> /snap/core18/current/lib64/ld-linux-x86-64.so.2
> >     #11 0x00007f8ce22c83ad in ?? () from
> /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #12 0x00007f8ce22c92df in _dl_catch_exception () from
> > /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #13 0x00007f8ce22c936f in _dl_catch_error () from
> /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #14 0x00007f8ce22c84d9 in __libc_dlopen_mode () from
> > /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #15 0x00007f8ce22aa886 in ?? () from
> /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #16 0x00007f8ce22ab088 in __nss_lookup_function () from
> > /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #17 0x00007f8ce2267cf3 in ?? () from
> /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #18 0x00007f8ce2269ce4 in getaddrinfo () from
> /snap/core18/current/lib/x86_64-linux-gnu/libc.so.6
> >     #19 0x0000000000671b31 in Fmake_network_process ()
>
> Looks like some problem with your system libraries: the crash is deep
> inside the C library.
>

[-- Attachment #2: Type: text/html, Size: 4241 bytes --]

  reply	other threads:[~2020-05-13 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE-NPOhLZKWJYmNP2ZxGz0zLZszsnxB8ot8CTAE_4zLRNLCebg@mail.gmail.com>
2020-05-13 17:41 ` bug#41240: 26.3; crash on startup when running package-refresh-contents Steve Lorimer
2020-05-13 18:12   ` Eli Zaretskii
2020-05-13 19:00     ` Steve Lorimer [this message]
2020-05-13 19:13       ` Eli Zaretskii

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CAE-NPOh-5M0ATk4i28par0D=ojaMRr2uF1WXqNBnrZNGwuBHtg@mail.gmail.com' \
    --to=steve.lorimer@gmail.com \
    --cc=41240@debbugs.gnu.org \
    --cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).