From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.bugs Subject: bug#21313: 25.0.50; Strange errors from dbus-handle-event Date: Fri, 02 Oct 2015 22:33:08 +0200 Message-ID: <87twq9roxn.fsf@gnu.org> References: <877foo4nkd.fsf@gnu.org> <87wpvzs4r3.fsf@gnu.org> <87bnd9cf7g.fsf@gnu.org> <831te53zbq.fsf@gnu.org> <871te5cdg7.fsf@gnu.org> <83wpvx2h16.fsf@gnu.org> <87r3lziti9.fsf@gnu.org> <83zj0n7jtl.fsf@gnu.org> <87wpvjovfu.fsf@gnu.org> <877fnikhms.fsf@gmail.com> <87oaguq2yw.fsf@gnu.org> <8737xtt8wt.fsf@gnu.org> <834mi95bx1.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1443818696 22594 80.91.229.3 (2 Oct 2015 20:44:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Oct 2015 20:44:56 +0000 (UTC) Cc: rpluim@gmail.com, 21313@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Oct 02 22:44:43 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1Zi7C5-0001c8-Jg for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 Oct 2015 22:44:41 +0200 Original-Received: from localhost ([::1]:35112 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi7C5-0002tp-01 for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 Oct 2015 16:44:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54760) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi71r-0004BM-IJ for bug-gnu-emacs@gnu.org; Fri, 02 Oct 2015 16:34:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zi71m-000667-Hy for bug-gnu-emacs@gnu.org; Fri, 02 Oct 2015 16:34:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35271) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zi71m-00065v-EJ for bug-gnu-emacs@gnu.org; Fri, 02 Oct 2015 16:34:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Zi71m-0002Qd-5Q for bug-gnu-emacs@gnu.org; Fri, 02 Oct 2015 16:34:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Tassilo Horn Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Oct 2015 20:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21313 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 21313-submit@debbugs.gnu.org id=B21313.14438179959282 (code B ref 21313); Fri, 02 Oct 2015 20:34:02 +0000 Original-Received: (at 21313) by debbugs.gnu.org; 2 Oct 2015 20:33:15 +0000 Original-Received: from localhost ([127.0.0.1]:52475 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Zi711-0002Pe-4H for submit@debbugs.gnu.org; Fri, 02 Oct 2015 16:33:15 -0400 Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]:40271) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Zi70y-0002PV-RU for 21313@debbugs.gnu.org; Fri, 02 Oct 2015 16:33:14 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E63EF201E8 for <21313@debbugs.gnu.org>; Fri, 2 Oct 2015 16:33:10 -0400 (EDT) Original-Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 02 Oct 2015 16:33:10 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=2y8Jrx0r8CnJVbrtOM8APZX6pj8=; b=XJ3Ck VpM0oF/kruj7+bFFASauFuTGURRIXUzLMedMNNuMlSSmBkDvhVdT+rnXHXBGCQm1 O2HpZC9U+XopRNXf5HfyAAD97KScYPpQnKvRNsXvQYe+EcZ+U8JRmZsOO/w4ohkj fjZoLNP2Ump3f5EgbFvYVneJpu6xWfCuGBRZ14= X-Sasl-enc: qQPCtaMsZOC2I6FNEuGtlTqqsWKXz25FJdjO6bFxpfEC 1443817990 Original-Received: from thinkpad-t440p (unknown [2.161.209.103]) by mail.messagingengine.com (Postfix) with ESMTPA id 25EEF6800ED; Fri, 2 Oct 2015 16:33:10 -0400 (EDT) In-Reply-To: <834mi95bx1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Oct 2015 22:05:14 +0300") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:107227 Archived-At: Eli Zaretskii writes: >> apparently my commits Next strangeness: in this very mail I wanted to kill all lines until the one below but apparently the line above was skipped. View lossage says ... C-k [kill-line] [next-line] C-k [kill-line] ... but I've never pressed . And another thing which occurs to me recently (which might be completely unrelated) is that I visit a file, and the effect of any key I type becomes visible only after the next key has been pressed. >> Should I revert these two commits? > > I understand those commits made the situation better, perhaps even > much better. If that's correct, I see no reason to revert them, I had that feeling initially but it might be completely subjective and wrong. Maybe I just didn't write email too often on these better days, I don't know. But the last few days were horrible again. > just to continue investigating the problem. Yes, of course. > One idea for investigation would be to write special code that would > collect data about these events, from the moment they are detected by > pselect until they wind up in the D-bus handler, and put that data > into a data structure accessible from Lisp. Then you could examine > that data when the problem happens, and analyze it. Well, yes, but I have no idea how to do that. As far as I understand, that loop that I've patched is the thing which calls callbacks which read input from file descriptors in order to create Dbus or file-notify events. Looking at the last error Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p CHARACTER_POSITION) dbus-handle-event((dbus-event FILE_NAME CHARACTER_POSITION LINE_NUMBER COLUMN_NUMBER OWNER_OS HOST_NAME USER CLASS NAME ATOM INTEGER SAVE_TARGETS)) funcall-interactively(dbus-handle-event (dbus-event FILE_NAME CHARACTER_POSITION LINE_NUMBER COLUMN_NUMBER OWNER_OS HOST_NAME USER CLASS NAME ATOM INTEGER SAVE_TARGETS)) call-interactively(dbus-handle-event nil [(dbus-event FILE_NAME CHARACTER_POSITION LINE_NUMBER COLUMN_NUMBER OWNER_OS HOST_NAME USER CLASS NAME ATOM INTEGER SAVE_TARGETS)]) command-execute(dbus-handle-event nil [(dbus-event FILE_NAME CHARACTER_POSITION LINE_NUMBER COLUMN_NUMBER OWNER_OS HOST_NAME USER CLASS NAME ATOM INTEGER SAVE_TARGETS)] t) the thing passed to `dbus-handle-event' looks like a dbus event except that its contents are bogus. These events are created by xd_read_message_1 in dbusbind.c, however that function is reasonable strict and could not create the bogus event above, e.g., it calls make_number on the event type which becomes the second item in a dbus-event, i.e., the CHARACTER_POSITION above which is no number. So what should that tell us? I don't really know. Bye, Tassilo