GNU bug report logs - #29548
25.2; How to DEBUG get-device-terminal

Previous Next

Package: emacs;

Reported by: Live System User <nyc4bos <at> aol.com>

Date: Sun, 3 Dec 2017 15:43:01 UTC

Severity: normal

Tags: moreinfo, wontfix

Merged with 22362, 23378

Found in versions 24.5, 25.0.92, 25.2

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #40 received at 29548 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Live System User <nyc4bos <at> aol.com>
Cc: martin rudalics <rudalics <at> gmx.at>, 29548 <at> debbugs.gnu.org
Subject: Re: bug#29548: 25.2; How to DEBUG get-device-terminal
Date: Tue, 09 Jan 2018 22:51:47 -0500
Live System User <nyc4bos <at> aol.com> writes:

> Noam Postavsky <npostavs <at> users.sourceforge.net> writes:
>
>> Hmm, if you can reproduce this semi-regularly, then perhaps the
>> following patch can catch the reason for the problem.  It sets a
>> breakpoint in Fsignal while the terminal is in the process of being

I said Fsignal, but posted a patching breaking in signal_or_quit.  The
latter only exists in emacs-26.  Are you running that or 25.2 as in your
original report?

Actually I think it might work better to break in longjmp instead.

> Thread 1 "emacs" hit Breakpoint 3, begin_delete_terminal () at terminal.c:317
> 317	    delete_terminal_count++;
>
>
>    I noticed that this didn't end with a paired
>
>              "delete_terminal_count--;".
>              
>    which it does do so normally.

I believe this means that the problem is indeed a non-local exit
happening somewhere in there, but we failed to catch it.  Either because
I posted the Emacs 26 version while you are on Emacs 25, or it doesn't
go through the signal machinery at all.




This bug report was last modified 6 years and 134 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.