From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: eggert@cs.ucla.edu, 12814@debbugs.gnu.org
Subject: bug#12814: 24.3.50; Emacs crash in event_to_kboard at keyboard.c:3421
Date: Wed, 07 Nov 2012 21:19:17 +0200 [thread overview]
Message-ID: <83lied1aru.fsf@gnu.org> (raw)
In-Reply-To: <87lieddzge.fsf@thinkpad.tsdh.de>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: eggert@cs.ucla.edu, 12814@debbugs.gnu.org
> Date: Wed, 07 Nov 2012 19:45:21 +0100
>
> the next crash occured. This time not while typing but while scrolling
> (<down>) in an info buffer.
If you were scrolling down, how come Emacs was processing a selection
request event? AFAIK, that means some other application requested the
selection data owned by Emacs.
> (gdb) p *event
> $3 = {
> kind = SELECTION_REQUEST_EVENT,
> code = 54395952,
> part = 23068704,
> modifiers = 0,
> x = 400,
> y = 322,
> timestamp = 356,
> frame_or_window = 2922261,
> arg = 12766914
> }
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.
next prev parent reply other threads:[~2012-11-07 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 10:56 bug#12814: 24.3.50; Emacs crash in event_to_kboard at keyboard.c:3421 Tassilo Horn
2012-11-06 15:13 ` Tassilo Horn
2012-11-06 16:16 ` Eli Zaretskii
2012-11-06 18:11 ` Tassilo Horn
2012-11-06 18:27 ` Tassilo Horn
2012-11-06 19:08 ` Eli Zaretskii
2012-11-06 20:01 ` Tassilo Horn
2012-11-06 20:21 ` Eli Zaretskii
2012-11-06 20:50 ` Paul Eggert
2012-11-06 20:54 ` Tassilo Horn
2012-11-06 21:04 ` Paul Eggert
2012-11-06 21:20 ` Tassilo Horn
2012-11-06 21:29 ` Eli Zaretskii
2012-11-07 11:39 ` Tassilo Horn
2012-11-07 17:17 ` Eli Zaretskii
2012-11-07 18:45 ` Tassilo Horn
2012-11-07 19:19 ` Eli Zaretskii [this message]
2012-11-08 7:56 ` Tassilo Horn
2012-11-08 9:30 ` Dmitry Antipov
2012-11-08 10:55 ` Tassilo Horn
2012-11-12 7:34 ` Tassilo Horn
2012-11-06 21:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lied1aru.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12814@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=tsdh@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.