From: Mark Oteiza <mvoteiza@udel.edu>
To: 16674@debbugs.gnu.org
Subject: bug#16674: 24.3.50; crash: redisplay_internal, update_frame, using client-daemon in tmux
Date: Wed, 09 Apr 2014 15:30:37 -0400 [thread overview]
Message-ID: <87y4zejo6a.fsf@holos.localdomain> (raw)
In-Reply-To: <87sirwvsr0.fsf@holos.localdomain>
Eli Zaretskii <eliz@gnu.org> writes:
>> >> This does not happen in 24.3, so this is a regression I imagine I can
>> >> bisect if need be.
>> >
>> > Please do, and thanks.
>>
>> I found 0cd28af (references Bug#15025).
>
> Dmitry, this is bzr revision 113891. Perhaps the new code in
> delete_frame should include a few more tests from candidate_frame?
> (That's just a wild guess, though: I don't really understand what does
> tmux do to Emacs -- are we selecting a frame that is no longer
> displayed or something?)
I looked at Bug#15025 and figured the recipe here can be simpler:
1. emacs --daemon -Q
2. open two xterms
3. do `emacsclient -t` in both
4. exit one emacsclient
The remaining emacsclient has no focus. Resizing the xterm has no
effect on the client.
Out of curiosity, I tried reverting r113891 (g0cd28af). As expected,
I could reproduce Bug#15025.
I still have not found a recipe for reproducing the crash. Is there any
debugging I can do to help the issue?
next prev parent reply other threads:[~2014-04-09 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 21:25 bug#16674: 24.3.50; crash: redisplay_internal, update_frame, using client-daemon in tmux Mark Oteiza
2014-02-07 7:16 ` Eli Zaretskii
2014-02-07 16:06 ` Mark Oteiza
2014-02-08 10:41 ` Eli Zaretskii
2014-02-09 7:39 ` Mark Oteiza
2014-02-09 17:27 ` Eli Zaretskii
2014-04-09 19:30 ` Mark Oteiza [this message]
2014-07-26 16:23 ` Mark Oteiza
2014-07-26 16:31 ` Eli Zaretskii
2014-07-27 13:07 ` Eli Zaretskii
2014-07-27 15:24 ` Mark Oteiza
2014-07-27 16:24 ` Eli Zaretskii
[not found] ` <87d2cqoid8.fsf@holos.localdomain>
2014-07-27 17:39 ` Eli Zaretskii
2014-07-27 17:50 ` Mark Oteiza
2014-07-28 6:34 ` 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=87y4zejo6a.fsf@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=16674@debbugs.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).