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#12814: 24.3.50; Emacs crash in event_to_kboard at keyboard.c:3421 Date: Thu, 08 Nov 2012 08:56:05 +0100 Message-ID: <87fw4k1qay.fsf@thinkpad.tsdh.de> References: <87objb0zlc.fsf@thinkpad.tsdh.de> <871ug63gu3.fsf@thinkpad.tsdh.de> <83k3ty3dwe.fsf@gnu.org> <87pq3qr48g.fsf@thinkpad.tsdh.de> <87390md1st.fsf@thinkpad.tsdh.de> <83a9uu35x4.fsf@gnu.org> <87y5ie33hl.fsf@thinkpad.tsdh.de> <838vae32jd.fsf@gnu.org> <5099780E.4090308@cs.ucla.edu> <87zk2uh2pv.fsf@thinkpad.tsdh.de> <83390m2zez.fsf@gnu.org> <87bof93ane.fsf@thinkpad.tsdh.de> <83obj91ges.fsf@gnu.org> <87lieddzge.fsf@thinkpad.tsdh.de> <83lied1aru.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1352361435 20508 80.91.229.3 (8 Nov 2012 07:57:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 8 Nov 2012 07:57:15 +0000 (UTC) Cc: eggert@cs.ucla.edu, 12814@debbugs.gnu.org To: Eli Zaretskii , Dmitry Antipov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Nov 08 08:57:25 2012 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 1TWMzM-0004U5-2n for geb-bug-gnu-emacs@m.gmane.org; Thu, 08 Nov 2012 08:57:24 +0100 Original-Received: from localhost ([::1]:47127 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TWMzC-0005s9-TK for geb-bug-gnu-emacs@m.gmane.org; Thu, 08 Nov 2012 02:57:14 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:41920) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TWMz3-0005r9-Qm for bug-gnu-emacs@gnu.org; Thu, 08 Nov 2012 02:57:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TWMyz-0005pY-PW for bug-gnu-emacs@gnu.org; Thu, 08 Nov 2012 02:57:05 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:45064) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TWMyz-0005pU-M4 for bug-gnu-emacs@gnu.org; Thu, 08 Nov 2012 02:57:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TWMyz-00045S-Ox for bug-gnu-emacs@gnu.org; Thu, 08 Nov 2012 02:57:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Tassilo Horn Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 08 Nov 2012 07:57:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 12814 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 12814-submit@debbugs.gnu.org id=B12814.135236137315657 (code B ref 12814); Thu, 08 Nov 2012 07:57:01 +0000 Original-Received: (at 12814) by debbugs.gnu.org; 8 Nov 2012 07:56:13 +0000 Original-Received: from localhost ([127.0.0.1]:55315 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TWMyD-00044T-8z for submit@debbugs.gnu.org; Thu, 08 Nov 2012 02:56:13 -0500 Original-Received: from deliver.uni-koblenz.de ([141.26.64.15]:44568) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TWMyB-00044N-HG for 12814@debbugs.gnu.org; Thu, 08 Nov 2012 02:56:12 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by deliver.uni-koblenz.de (Postfix) with ESMTP id AB44FD238C; Thu, 8 Nov 2012 08:56:10 +0100 (CET) X-Virus-Scanned: amavisd-new at uni-koblenz.de Original-Received: from deliver.uni-koblenz.de ([127.0.0.1]) by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtGc_wN4K1DF; Thu, 8 Nov 2012 08:56:10 +0100 (CET) X-CHKRCPT: Envelopesender noch tsdh@gnu.org Original-Received: from thinkpad.tsdh.de (tsdh.uni-koblenz.de [141.26.67.142]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by deliver.uni-koblenz.de (Postfix) with ESMTPSA id E4538D238B; Thu, 8 Nov 2012 08:56:09 +0100 (CET) In-Reply-To: <83lied1aru.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 07 Nov 2012 21:19:17 +0200") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.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:66620 Archived-At: Eli Zaretskii writes: >> the next crash occured. This time not while typing but while >> scrolling () in an info buffer. > > If you were scrolling down, how come Emacs was processing a selection > request event? I have no clue. The crash just happened again while typing in a mail, and it also was a SELECTION_REQUEST_EVENT with inaccessible frame_or_window. > AFAIK, that means some other application requested the selection data > owned by Emacs. Hm, I'm running a GNOME3 desktop. Right now, there are only some terminals running and a browser. Ah, and the parcellite clipboard manager. But those haven't been updated lately, and a week ago, emacs didn't crash. > Someone who knows their way around X selection code should help you > find out where does this value of frame_or_window come from, and how > that Lisp object became inaccessible. Looking at the ChangeLog, this one looks suspicious to me: 2012-11-02 Dmitry Antipov Remove pad from struct input_event. * termhooks.h (struct input_event): Remove padding field. Adjust comment. * keyboard.c (event_to_kboard): Simplify because frame_or_window member is never cons for a long time. Adjust comment. (mark_kboards): Adjust because SELECTION_REQUEST_EVENT and SELECTION_CLEAR_EVENT has no Lisp_Objects to mark. Add comment. * xterm.c (handle_one_xevent): Do not initialize frame_or_window field of SELECTION_REQUEST_EVENT and SELECTION_CLEAR_EVENT. It would fit the time frame since when the crashes appeared first. Bye, Tassilo