From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: Fatal error 11: Segmentation Fault
Date: Tue, 02 Apr 2019 17:50:42 +0200 [thread overview]
Message-ID: <86a7h85ru5.fsf@zoho.eu> (raw)
In-Reply-To: fa8afb1f-948c-481c-805a-c3161e0eafff@default
Drew Adams wrote:
>>> 'emacs -Q' works but byte-compiling
>>> doesn't complain.
>> 'emacs -q' works.
>
> Haven't been following this thread, but if
> those both work then bisect your init file to
> find the culprit.
>
> But Emacs shouldn't crash in any case, so
> you'll likely want to file a bug report once
> you get a minimal recipe to repro the crash.
> (`M-x report-emacs-bug'.)
If it is in my init files, how come it
works once? I type this using Emacs.
Besides, doing a "binary search" isn't so easy.
Many files are interconnected. To mot load one
file does mean commenting out `require's in
lots'a others, as well as functions who uses
their stuff, then functions that uses those
functions, and so on.
Can't I use gdb or something to find it?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-04-02 15:50 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a7h85ru5.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.