[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#36716: 27.0.50; Emacs crushes in console after X session, but not in
From: |
Jean Louis |
Subject: |
bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen |
Date: |
Thu, 18 Jul 2019 17:13:06 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
* Eli Zaretskii <eliz@gnu.org> [2019-07-18 17:05]:
> This part of your original traceback:
>
> > /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]
>
> seems to be very much like the one described in this GPM bug report:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888792
>
> From the discussion there, you may wish to consider upgrading to a
> newer version of GPM.
I have now recompiled from git, without GPM, and
it does not crash.
If it works with the newer GPM, good.
Thank you,
Jean
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Jean Louis, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Eli Zaretskii, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Jean Louis, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Eli Zaretskii, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Jean Louis, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Eli Zaretskii, 2019/07/18
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen,
Jean Louis <=
- bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen, Eli Zaretskii, 2019/07/18