From: Eli Zaretskii <eliz@gnu.org>
To: "Mário Sousa" <sargedas@lip.pt>
Cc: 26218@debbugs.gnu.org
Subject: bug#26218: 25.1; crash during run time
Date: Wed, 22 Mar 2017 22:41:34 +0200 [thread overview]
Message-ID: <83mvcd59j5.fsf@gnu.org> (raw)
In-Reply-To: <CACkc6r5YPxmYhos6TM468ghAUuOtbxwqxvce5HSs40ZN4h1fSA@mail.gmail.com> (message from Mário Sousa on Wed, 22 Mar 2017 20:32:50 +0000)
> From: Mário Sousa <sargedas@lip.pt>
> Date: Wed, 22 Mar 2017 20:32:50 +0000
> Cc: Mario Sousa <sargedas@lip.pt>, 26218@debbugs.gnu.org
>
> Thanks for the quick reply.
> I am a favourite of emacs since a long time now.
> The program is crashing sometimes repeatedly and some times I can work on it for hours/days without
> closing with no problem.
> The email I have sent through emacs happen after the crash (I though it would save the information from the
> crash). I saw in the internet how to do the automatic. This (below) is the message that comes from the crash.
> Maybe you can interpreted it.
>
> Tell me what more information should I send you.
>
> --
> Best regards
> Mário Sousa
>
> ++++++
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x50ac9c]
Thanks. Please run Emacs under GDB, and when it crashes, type this
command at GDB prompt:
(gdb) thread apply all bt
Then post here everything that GDB displays in response to the above
command. This will provide a human-readable backtrace that we could
analyze and attempt to understand what causes the crashes.
next prev parent reply other threads:[~2017-03-22 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:18 bug#26218: 25.1; crash during run time Mario Sousa
2017-03-22 19:57 ` Eli Zaretskii
2017-03-22 20:32 ` Mário Sousa
2017-03-22 20:41 ` Eli Zaretskii [this message]
[not found] ` <CACkc6r7qAH7cPqq_SgaHoZ5QbPO=gxBPiR=_rcm-SOMWZEvwDA@mail.gmail.com>
[not found] ` <CACkc6r7CZ15c9KO4_J5Z2HonTe7N_1+ffLa+Wbz1anTQj=uC5Q@mail.gmail.com>
2017-03-22 21:09 ` Mário Sousa
2017-03-23 3:31 ` 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=83mvcd59j5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26218@debbugs.gnu.org \
--cc=sargedas@lip.pt \
/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.