From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dann@ics.uci.edu, 4970@emacsbugs.donarmstrong.com
Subject: bug#4970: 23.1; Emacs Gtk running nuts
Date: Fri, 20 Nov 2009 13:11:15 +0100 [thread overview]
Message-ID: <4B068763.8040509@swipnet.se> (raw)
In-Reply-To: <83ws1lphwp.fsf@gnu.org>
Eli Zaretskii skrev:
>> Date: Fri, 20 Nov 2009 11:37:01 +0100
>> From: Jan =?UTF-8?Q?Dj=C3=A4rv?= <jan.h.d@swipnet.se>
>> Cc: 4970@emacsbugs.donarmstrong.com
>>
>> Dan Nicolaescu skrev:
>>> Jan Djärv <jan.h.d@swipnet.se> writes:
>>>
>>> > What happens is that reading from the terminal fails and Emacs tries
>>> > to remove that terminal, but in term.c:
>>> >
>>> > if (last_terminal)
>>> > error ("Attempt to delete the sole terminal device with live frames");
>>> >
>>> >
>>> > which goes back to the command loop, tries to read agan, fails, and
>>> > tries to delete the terminal again, and so on.
>>> >
>>> > If you remove this check, Emacs exits. But I suppose it is there for
>>> > a reason, but I don't know what. Anybody?
>>>
>>> It's there so that if you do:
>>> emacs -Q -nw
>>> C-x 5 0
>>> does not exit emacs.
>> Well, the check in term.c isn't preventing that. It is the check in frame.c
>> delete_frame that does that:
>>
>> if (NILP (force) && !other_visible_frames (f))
>> error ("Attempt to delete the sole visible or iconified frame");
>
> What about delete-terminal?
Rhat check in term.c prevents delete-terminal from working when the FORCE
argument is t. Deleting an X11 terminal woth FORCE set to t makes a core dump...
>
> And btw, are there any live frames when the test in term.c is made, in
> the recipe to reproduce the original bug? If not, maybe it needs to
> check for live frames explicitly.
Yes there are. When read_socket_hook returns -2 and this is the last terminal,
a SIGHUP is sent to ourselves (why not just call shutdown_emacs and exit?) and
Fdelete_terminal is called. So frames has not been removed yet.
Jan D.
next prev parent reply other threads:[~2009-11-20 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 13:44 bug#4970: 23.1; Emacs Gtk running nuts Dr. Werner Fink
2009-11-25 18:02 ` Jan Djärv
2009-11-19 10:34 ` Werner Fink
2009-11-19 19:56 ` Dan Nicolaescu
2009-11-20 8:31 ` Jan Djärv
2009-11-20 9:11 ` Dan Nicolaescu
2009-11-20 10:37 ` Jan Djärv
2009-11-20 11:14 ` Eli Zaretskii
2009-11-20 12:11 ` Jan Djärv [this message]
2009-11-20 13:11 ` Eli Zaretskii
2009-11-20 16:44 ` Jan Djärv
2009-11-20 16:05 ` Dan Nicolaescu
2009-11-25 18:10 ` bug#4970: marked as done (23.1; Emacs Gtk running nuts) Emacs bug Tracking System
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=4B068763.8040509@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=4970@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
--cc=eliz@gnu.org \
/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).