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: Wed, 14 Oct 2015 21:37:17 +0200 Message-ID: <876129gs2a.fsf@gnu.org> References: <877foo4nkd.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> <87twq9roxn.fsf@gnu.org> <83wpv53rjn.fsf@gnu.org> <87h9m9rmgk.fsf@gmx.de> <87wpv4qzm2.fsf@gnu.org> <87a8s0v1lp.fsf@gmx.de> <87twq8gyk0.fsf@gnu.org> <87lhbk47hb.fsf@gnu.org> <83d1ww4416.fsf@gnu.org> <878u75rctw.fsf@gnu.org> <836129xtx8.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444851576 3384 80.91.229.3 (14 Oct 2015 19:39:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 14 Oct 2015 19:39:36 +0000 (UTC) Cc: michael.albinus@gmx.de, 21313@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 14 21:39:20 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 1ZmRtK-0002B0-KV for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Oct 2015 21:39:14 +0200 Original-Received: from localhost ([::1]:44191 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmRtJ-0006Ht-Vc for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Oct 2015 15:39:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34997) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmRsD-0006As-7p for bug-gnu-emacs@gnu.org; Wed, 14 Oct 2015 15:38:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZmRsA-0005Po-H1 for bug-gnu-emacs@gnu.org; Wed, 14 Oct 2015 15:38:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:60447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZmRsA-0005Pc-DC for bug-gnu-emacs@gnu.org; Wed, 14 Oct 2015 15:38:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZmRsA-0004gK-1P for bug-gnu-emacs@gnu.org; Wed, 14 Oct 2015 15:38:02 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: <877foo4nkd.fsf@gnu.org> Resent-From: Tassilo Horn Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 14 Oct 2015 19:38:01 +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.144485144417924 (code B ref 21313); Wed, 14 Oct 2015 19:38:01 +0000 Original-Received: (at 21313) by debbugs.gnu.org; 14 Oct 2015 19:37:24 +0000 Original-Received: from localhost ([127.0.0.1]:51155 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZmRrX-0004f1-Of for submit@debbugs.gnu.org; Wed, 14 Oct 2015 15:37:24 -0400 Original-Received: from out3-smtp.messagingengine.com ([66.111.4.27]:59789) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZmRrU-0004eq-W3 for 21313@debbugs.gnu.org; Wed, 14 Oct 2015 15:37:22 -0400 Original-Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7A8D720A33 for <21313@debbugs.gnu.org>; Wed, 14 Oct 2015 15:37:20 -0400 (EDT) Original-Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 14 Oct 2015 15:37:20 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:references:subject:to:x-sasl-enc:x-sasl-enc; s= smtpout; bh=m7Mp6SZ2ehsYU3NHzq5+7AT8G/g=; b=DvCTOIFYEuCLeCdNm1jA FynnZYW/F17Bgk2B5yM14LDGm7Q0sdu70J2jWiHKovAJ8ryujJES4PYjcwRvogoP YzyOhXzU57nUoJP/SCuPyNa/nJBiS2QoBsY2/kLxkFNzdoEArAq8lWIEag7K4FN8 LV5HkFivLXlkW1/sOxbxtOI= X-Sasl-enc: PfJsOYknu3ijxxIQMR35ydltxs7RRGUAwlU/q5sXyJ1c 1444851440 Original-Received: from thinkpad-t440p (unknown [2.160.102.251]) by mail.messagingengine.com (Postfix) with ESMTPA id AA6D0C00014; Wed, 14 Oct 2015 15:37:19 -0400 (EDT) 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:107619 Archived-At: Eli Zaretskii writes: >> > There's also 30a6b1f81412044aa7dda5573b0142a0a03c4fd3, although it >> > was supposed to deal only with recording input events for the >> > purposes of keyboard macros. >> >> I've been running with the latest master with that single commit >> reverted for the past 10 days and never had this issue again. So I'm >> tempted to say that this commit is most probably the culprit. > > The only effect of that change is to call record_char on some events > that might have evaded that before. record_char does 2 things: > > . it adds the event to recent-keys, a Lisp array > . it records the event as part of a keyboard macro, if a macro is > being recorded > > (There's also the "dribble" part, but I doubt that you are running > with that enabled.) No, I don't run that. > So I wonder how could any of that cause the kind of trouble you > reported. Me, too. > If you undo the revert of that commit, do you start seeing the problem > again? I'm back on master now so we'll see. > If you do, please see which of the "unusual" events, if any, get > passed to record_char, and whether they are recorded as part of > recent-keys and keyboard macros I added some debug code which spits out something like record_char: 107 -> NOT storing as part of macro -2> set to recent_keys at index 28 where the 107 is the result of formatting the Lisp_Object with "%S", the second line indicates if store_kbd_macro_char is doing something, and the -2> line means that the second ASET (recent_keys, ...) invocation in record_char has been executed. That's what you had in mind, right? > (assuming that you are used to define and invoke macros in your > routine work). Yes, but not too frequently. Macros haven't been involved when I had those issues unless it is possible that some macro recording/replaying I've done much earlier could have had a side-effect which appears much later when killing text in a message-mode buffer. Bye, Tassilo