From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mike Kupfer Newsgroups: gmane.emacs.devel Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes Date: Wed, 17 Feb 2016 21:01:15 -0800 Message-ID: <1027.1455771675@allegro.localdomain> References: <83d1rvumux.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: ger.gmane.org 1455771707 30316 80.91.229.3 (18 Feb 2016 05:01:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Feb 2016 05:01:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 18 06:01:36 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aWGie-0004dj-1g for ged-emacs-devel@m.gmane.org; Thu, 18 Feb 2016 06:01:36 +0100 Original-Received: from localhost ([::1]:36941 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWGid-0002o5-6P for ged-emacs-devel@m.gmane.org; Thu, 18 Feb 2016 00:01:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWGiQ-0002nu-Fb for emacs-devel@gnu.org; Thu, 18 Feb 2016 00:01:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aWGiN-0008Jr-9f for emacs-devel@gnu.org; Thu, 18 Feb 2016 00:01:22 -0500 Original-Received: from shell1.rawbw.com ([198.144.192.42]:57600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWGiM-0008Jh-Vm; Thu, 18 Feb 2016 00:01:19 -0500 Original-Received: from allegro.localdomain (m208-249.dsl.rawbw.com [198.144.208.249]) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id u1I51Fgh037438; Wed, 17 Feb 2016 21:01:15 -0800 (PST) (envelope-from m.kupfer@acm.org) X-Authentication-Warning: shell1.rawbw.com: Host m208-249.dsl.rawbw.com [198.144.208.249] claimed to be allegro.localdomain In-Reply-To: Your message of "Wed, 17 Feb 2016 22:02:14 +0200." <83d1rvumux.fsf@gnu.org> X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 25.0.91 Content-ID: <1026.1455771675.1@allegro.localdomain> X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x X-Received-From: 198.144.192.42 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200115 Archived-At: As suggested, I've opened a bug for this: #22728. Eli Zaretskii wrote: > > From: Mike Kupfer > > cc: emacs-devel@gnu.org > > Date: Tue, 16 Feb 2016 18:05:52 -0800 > > > > 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). > > This means Emacs started creating the frame, but didn't finish that > process. A new frame is recorded in the frame list only when it is > completely set up. The question is: what happens during that process > which prevents it from completing? > > At this point, it looks like instrumenting x-create-frame to write > traces to some file might tell what causes that function to stop doing > its job half way through. Okay. If someone provides a patch, I'd be happy to apply it on the systems I run Emacs on. I can also look at instrumenting x-create-frame myself. That will take longer to set up, but given how long it is between occurrences of this problem, some initial delay probably doesn't matter much. I wonder if the problem is particular to a certain widget set. If anyone has suggestions for instrumenting the Athena (2D) widget set, I'd welcome them. > > And I still think it's suspicious that the bad frame seems to match a > > frame that was deleted earlier. > > Was the deleted frame deleted from the frame list? I'm not sure I understand the question. The frame list that I looked at on the 15th had these 3 frames: (# # #) (This was after the bad frame was created.) The log showed the deletion of # on the 12th, and the creation of # on the 15th. Let me know if that doesn't answer your question. thanks and regards, mike