From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: Fatal error 11: Segmentation Fault
Date: Wed, 03 Apr 2019 03:20:23 +0200 [thread overview]
Message-ID: <87sguzyje0.fsf@telefonica.net> (raw)
In-Reply-To: 86o95o3pzk.fsf@zoho.eu
Emanuel Berg <moasenwood@zoho.eu> writes:
>> (info "(emacs) Checklist")
>
> It says one should execute Emacs in the same
> directory as the source, but I have my emacs25
> from the Raspbian repos. (I have the
> emacs25-src pack but I suspect that isn't what
> is refered to.)
emacs25-dbg (if exists in Raspbian) is needed for readable stack traces.
> The source my Emacs was installed from isn't
> still on my computer (with apt-get/aptitude),
> right?
If you have emacs25-src installed, you have the source, I suppose.
> Also it isn't clear IMO exactly what to do,
> more of a tech discussion and lots of what
> _not_ to do.
>
> I don't say there is a silver bullet solution,
> more like a paragraph could be "If you have no
> clue what's going on, do this as a best-effort
> first move..."
Okay, after installing emacs25-dbg, do this:
$ gdb emacs
(gdb) run
<... use emacs until it crashes ...>
(gdb) backtrace
(gdb) xbacktrace
Copy the output of the last two commands and paste them on the buffer
created by M-x report-emacs-bug.
To exit GDB:
(gdb) quit
<... if it asks for a confirmation, say `y'...>
next prev parent reply other threads:[~2019-04-03 1:20 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
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 [this message]
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=87sguzyje0.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).