unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Kupfer <m.kupfer@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes
Date: Tue, 16 Feb 2016 18:05:52 -0800	[thread overview]
Message-ID: <23781.1455674752@allegro.localdomain> (raw)
In-Reply-To: Your message of "Tue, 16 Feb 2016 18:26:53 +0200." <83fuwswrhu.fsf@gnu.org>

Eli Zaretskii wrote:

> > From: Mike Kupfer <m.kupfer@acm.org>
> > Here's the relevant excerpt from the server log for two emacsclient
> > invocations.  The first one is for the bad frame, the second one is for
> > a working frame.  I can provide the entire server log if desired.
> 
> I'm not sure the server log is the place to look for the problem.  Why
> did you think it was relevant?

Well, back in September when this was discussed, one of the suggestions
for the OP was to look into the "communications between emacsclient
and the server on the Emacs side, and see what is passed there."  When I
asked how to do this, I was pointed at the server log.

And the results do seem relevant.  I ran "emacsclient -c" twice within a
short period of time, and the server log showed 2 frames being created.
So *some* code in Emacs thought the first frame was created, even though
it didn't show up in the output from (frame-list).

And I still think it's suspicious that the bad frame seems to match a
frame that was deleted earlier.

> What kind of build is this?  (It's probably best to submit a formal
> bug report where all these details will be spelled out.)

It's a pretty vanilla build of 24.5 on Debian stable.

I'll go ahead and open a bug.

thanks,
mike



  parent reply	other threads:[~2016-02-17  2:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 13:00 Need help debugging Emacs: emacsclient will not draw its contents sometimes Jon Dufresne
2015-09-08 13:28 ` Tassilo Horn
2015-09-08 17:18 ` Eli Zaretskii
2015-09-08 18:58   ` Jon Dufresne
2015-09-08 19:16     ` Eli Zaretskii
2015-09-09 22:29       ` Jon Dufresne
2015-09-10 15:26         ` Eli Zaretskii
2015-09-10 18:20           ` Jon Dufresne
2015-09-10 18:46             ` Eli Zaretskii
2015-09-10 18:52               ` Jon Dufresne
2015-09-11  7:26                 ` Eli Zaretskii
2015-09-11 16:47                   ` Jon Dufresne
2015-09-14 10:09                     ` Eli Zaretskii
2015-09-23  0:51                       ` Jon Dufresne
2015-09-23  6:45                         ` Eli Zaretskii
2015-09-27 22:21                           ` Mike Kupfer
2015-09-28  6:39                             ` Eli Zaretskii
2016-02-16  1:07                             ` Mike Kupfer
2016-02-16 16:26                               ` Eli Zaretskii
2016-02-16 16:38                                 ` Kaushal Modi
2016-02-16 16:44                                   ` Eli Zaretskii
2016-02-16 17:06                                     ` Kaushal Modi
2016-02-17  2:05                                 ` Mike Kupfer [this message]
2016-02-17 20:02                                   ` Eli Zaretskii
2016-02-18  5:01                                     ` Mike Kupfer
2016-02-20 11:24                                       ` 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=23781.1455674752@allegro.localdomain \
    --to=m.kupfer@acm.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).