bug#36716: 27.0.50; Emacs crushes in console after X session, but not in screen

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 15:38:29 +0200
> From: Jean Louis <bugs@gnu.support>
> Cc: 36716@debbugs.gnu.org
> 
> * Eli Zaretskii <eliz@gnu.org> [2019-07-18 14:55]:
> > 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.
> 
> Thank you for pointers, here it is below.
> 
> emacs_backtrace at 
> /home/data1/protected/Programming/Software/emacs/src/sysdep.c:2437
> terminate_due_to_signal at 
> /home/data1/protected/Programming/Software/emacs/src/emacs.c:399
> handle_fatal_signal at 
> /home/data1/protected/Programming/Software/emacs/src/sysdep.c:1790
> deliver_thread_signal.constprop.7 at 
> /home/data1/protected/Programming/Software/emacs/src/sysdep.c:1764
> stack_overflow at 
> /home/data1/protected/Programming/Software/emacs/src/sysdep.c:1840
>  (inlined by) handle_sigsegv at 
> /home/data1/protected/Programming/Software/emacs/src/sysdep.c:1883
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> ?? ??:0
> Fgpm_mouse_start at 
> /home/data1/protected/Programming/Software/emacs/src/term.c:2623

Looks like some problem with GPM mouse?  What if you build Emacs
without GPM?

Can someone else who has Emacs built with GPM support reproduce this?