From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 36716@debbugs.gnu.org
Subject: bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen
Date: Thu, 18 Jul 2019 15:54:21 +0300 [thread overview]
Message-ID: <83wogfwlj6.fsf@gnu.org> (raw)
In-Reply-To: <86v9vzik4l.fsf@protected.rcdrun.com> (message from Jean Louis on Thu, 18 Jul 2019 14:48:26 +0200)
> From: Jean Louis <bugs@gnu.support>
> Date: Thu, 18 Jul 2019 14:48:26 +0200
>
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x504182]
> emacs[0x4172e9]
> emacs[0x50289e]
> emacs[0x502be3]
> emacs[0x502c20]
> /usr/lib/libpthread.so.0(+0x12230)[0x7f6755cd6230]
> /usr/lib/libc.so.6(strchrnul+0x23)[0x7f6754ea6e43]
> /usr/lib/libc.so.6(_IO_vfprintf+0xad)[0x7f6754e638bd]
> /usr/lib/libc.so.6(__vfprintf_chk+0x86)[0x7f6754f16066]
> /usr/lib/libc.so.6(__vsyslog_chk+0x18b)[0x7f6754f021bb]
> /usr/lib/libc.so.6(__syslog_chk+0x8f)[0x7f6754f0271f]
> /usr/lib/libgpm.so.2(gpm_report+0x112)[0x7f67576cdae2]
> /usr/lib/libgpm.so.2(+0x21b1)[0x7f67576cc1b1]
> emacs[0x4b0cda]
> emacs[0x566519]
> emacs[0x59f7a0]
> emacs[0x56606f]
> emacs[0x56645f]
> emacs[0x59f7a0]
> emacs[0x56606f]
> emacs[0x56645f]
> emacs[0x59f7a0]
> emacs[0x56645f]
> emacs[0x59f7a0]
> emacs[0x56645f]
> emacs[0x59f7a0]
> emacs[0x568cbc]
> emacs[0x5659b3]
> emacs[0x569598]
> emacs[0x564ebe]
> emacs[0x4ee40c]
> emacs[0x564e5c]
> emacs[0x4eb978]
> emacs[0x4f0806]
> emacs[0x4f0b24]
> emacs[0x418c7b]
> /usr/lib/libc.so.6(__libc_start_main+0xf1)[0x7f6754e3b511]
> emacs[0x41996a]
Please use the method described in the Emacs manual, in the node
"Crashing", to convert these addresses into a human-readable list of
source file names, function names, and line numbers. Then post the
result here.
next prev parent reply other threads:[~2019-07-18 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:48 bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen Jean Louis
2019-07-18 12:54 ` Eli Zaretskii [this message]
2019-07-18 13:38 ` Jean Louis
2019-07-18 14:02 ` Eli Zaretskii
2019-07-18 14:34 ` Jean Louis
2019-07-18 15:05 ` Eli Zaretskii
2019-07-18 15:13 ` Jean Louis
2019-07-18 15:26 ` 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=83wogfwlj6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36716@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).