unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Fatal error 11: Segmentation Fault
Date: Wed, 03 Apr 2019 10:08:43 +0300	[thread overview]
Message-ID: <83lg0refb8.fsf@gnu.org> (raw)
In-Reply-To: <865zrvh9fz.fsf@zoho.eu> (message from Emanuel Berg on Wed, 03 Apr 2019 08:47:12 +0200)

> From: Emanuel Berg <moasenwood@zoho.eu>
> Date: Wed, 03 Apr 2019 08:47:12 +0200
> 
> Move (package-initialize) from ~/.emacs [1] to
> elpa.el [2] then byte-compile [3] with 'emake',
> which is
> 
>     make $@ -s -C ~/.emacs.d/emacs-init # [4]

What does this do, exactly?

>     $ emacs --debug-init # works, but try again...
> 
>     $ emacs --debug-init # Fatal error 11: Segmentation fault

What happens if you invoke Emacs in the same way the 3rd, 4th,
etc. time?  Does it crash on every invocation except the first, or on
every second invocation, or something else?

> reset (package-initialize) from elpa.el to
> .emacs, do 'emake', and
> 
>     $ emacs # works
>     $ emacs # works

It is possible that some of your customizations write something to the
disk, and that triggers the problem the next time.

If you want to help us find the culprit, run Emacs under GDB (install
Emacs with symbols if needed), and file a bug report with the C
backtrace, using "M-x report-emacs-bug RET".  Continuing the
discussion here is unlikely to find the reason for the crashes.

Another alternative is to upgrade to Emacs 26, perhaps this problem
was already solved during development after Emacs 25.



  reply	other threads:[~2019-04-03  7:08 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  1:33 Fatal error 11: Segmentation Fault Emanuel Berg
2019-04-02  2:39 ` Emanuel Berg
2019-04-02  2:48   ` Drew Adams
2019-04-02 15:50     ` Emanuel Berg
2019-04-02 16:27       ` Drew Adams
2019-04-02 23:54         ` Emanuel Berg
2019-04-03  1:37           ` Drew Adams
2019-04-03  5:30             ` Emanuel Berg
2019-04-03  6:47               ` Emanuel Berg
2019-04-03  7:08                 ` Eli Zaretskii [this message]
2019-04-03  7:49                   ` Emanuel Berg
2019-04-03  8:18               ` tomas
2019-04-03 10:51                 ` Using 'git bisect' to pinpoint errors in .emacs. Was: " Vegard Vesterheim
2019-04-03 11:14                   ` Eli Zaretskii
2019-04-03 12:47                     ` Vegard Vesterheim
2019-04-03 14:48                     ` Emanuel Berg
2019-04-03 12:14                   ` Skip Montanaro
2019-04-03 12:30                     ` Eli Zaretskii
2019-04-03 14:52                       ` Emanuel Berg
2019-04-03 15:41                         ` Eli Zaretskii
2019-04-03 15:47                           ` Emanuel Berg
2019-04-03 14:35                   ` Emanuel Berg
2019-04-04  7:40                     ` Vegard Vesterheim
2019-04-03 14:34                 ` Emanuel Berg
2019-04-03 16:29                   ` tomas
2019-04-03 17:06                     ` Drew Adams
2019-04-03 19:19                       ` tomas
2019-04-03 17:41                     ` Robert Thorpe
2019-04-03 21:03                       ` Emanuel Berg
2019-04-03 21:07                         ` Robert Thorpe
2019-04-03 21:16                           ` Emanuel Berg
2019-04-03 20:56                     ` Emanuel Berg
2019-04-02 17:14       ` Óscar Fuentes
2019-04-02 23:56         ` Emanuel Berg
2019-04-03  0:05           ` Emanuel Berg
2019-04-03  0:13             ` Emanuel Berg
2019-04-03  1:20               ` Óscar Fuentes
2019-04-03  1:28                 ` Óscar Fuentes
2019-04-03  2:33                 ` Emanuel Berg
2019-04-03  2:39                   ` Emanuel Berg
2019-04-03  4:47                 ` Emanuel Berg
2019-04-03  5:23                   ` Eli Zaretskii
2019-04-03  5:31                     ` Emanuel Berg
2019-04-03  5:56                       ` Eli Zaretskii
2019-04-03  6:48                         ` Emanuel Berg
2019-04-03  6:59                           ` Eli Zaretskii
2019-04-03  7:51                             ` Emanuel Berg
2019-04-03  8:12                               ` Eli Zaretskii
2019-04-03 14:21                                 ` Emanuel Berg
2019-04-03 14:36                                   ` Eli Zaretskii
2019-04-03 14:57                                     ` Emanuel Berg
2019-04-03 15:48                                       ` Eli Zaretskii
2019-04-03 21:05                                         ` Emanuel Berg
2019-04-04 12:51                                           ` 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=83lg0refb8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).