unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Joe Corneli <joseph.corneli@hyperreal.enterprises>
Cc: 56869@debbugs.gnu.org
Subject: bug#56869: 29.0.50; segfault, "assertion 'GDK_IS_DEVICE (device)' failed"
Date: Tue, 16 Aug 2022 18:52:55 +0800	[thread overview]
Message-ID: <87h72cqx2w.fsf@yahoo.com> (raw)
In-Reply-To: <87r11g4hrv.fsf@Proteus> (Joe Corneli's message of "Tue, 16 Aug 2022 11:14:28 +0100")

Joe Corneli <joseph.corneli@hyperreal.enterprises> writes:

> joe@Proteus:~/emacs$ gdb src/emacs core.384524
> ...
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/home/joe/emacs/src/emacs'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  gdk_x11_device_manager_xi2_translate_event (xevent=<optimised out>, event=<optimised out>, 
>     display=<optimised out>, translator=<optimised out>) at ../../../../../gdk/x11/gdkdevicemanager-xi2.c:1794
> 1794	../../../../../gdk/x11/gdkdevicemanager-xi2.c: No such file or directory.
> [Current thread is 1 (Thread 0x7ffff2947040 (LWP 384524))]
> (gdb) l
> 1789	in ../../../../../gdk/x11/gdkdevicemanager-xi2.c

Sigh, I guess you need the source packages as well.  Not sure what that
would be on Debian.

Thanks in advance.





  reply	other threads:[~2022-08-16 10:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 13:08 bug#56869: 29.0.50; segfault, "assertion 'GDK_IS_DEVICE (device)' failed" Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02  1:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 14:17   ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 18:22     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03  1:14       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11  9:56         ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11 11:48           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-11 13:34             ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12  1:17               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 11:45                 ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 12:35                   ` Eli Zaretskii
2022-08-12 13:23                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 11:21                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 12:36                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 11:18                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 14:00                       ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16  0:58                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 10:14                           ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 10:52                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-16 14:36                               ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-17 13:47                                 ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-18  2:38                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-18 13:20                                     ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-19  1:42                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21  9:57                                         ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21 10:56                                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-21 11:00                                             ` Eli Zaretskii
2022-08-22  6:21                                               ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22  6:37                                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22 11:27                                                   ` Eli Zaretskii
2022-08-22 12:59                                                   ` Joe Corneli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03  9:13                                             ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h72cqx2w.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56869@debbugs.gnu.org \
    --cc=joseph.corneli@hyperreal.enterprises \
    --cc=luangruo@yahoo.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).