From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Leonardo Hernández" <leohdz172@proton.me>
Cc: 63614@debbugs.gnu.org
Subject: bug#63614: 29.0.91; PGTK Emacs crashes after clearing the clipboard
Date: Sun, 21 May 2023 08:51:30 +0800 [thread overview]
Message-ID: <87lehi1p7x.fsf@yahoo.com> (raw)
In-Reply-To: <253496c1-088b-b54f-3c64-1cc563e70f24@proton.me> ("Leonardo Hernández"'s message of "Sat, 20 May 2023 18:52:31 +0000")
Leonardo Hernández <leohdz172@proton.me> writes:
> Hello, I have been having issues with crashes running Emacs with PGTK
> on Wayland.
>
> To reproduce, open `emacs -Q`, then copy whatever you want with <M-w> or
> <C-w> and then copy another thing outside Emacs, for example, `wl-copy
> <<< "Copied text"`, then Emacs crashes.
>
> Backtrace:
> #0 0x00007f92636ac8ec in () at /usr/lib64/libc.so.6
> #1 0x00007f926365d3e2 in raise () at /usr/lib64/libc.so.6
> #2 0x0000563f0697d0a5 in terminate_due_to_signal (sig=11,
> backtrace_limit=<optimized out>) at emacs.c:464
> #3 0x0000563f0697def8 in handle_fatal_signal (sig=11) at sysdep.c:1783
> fatal = <optimized out>
> #4 deliver_thread_signal (handler=<optimized out>, sig=11) at sysdep.c:1775
> fatal = <optimized out>
> #5 deliver_fatal_thread_signal (sig=11) at sysdep.c:1795
> fatal = <optimized out>
> #6 handle_sigsegv (sig=11, siginfo=0x563f072243f0 <sigsegv_stack+64496>,
> arg=<optimized out>) at sysdep.c:1888
> fatal = <optimized out>
> #7 0x00007f926365d490 in <signal handler called> () at /usr/lib64/libc.so.6
> #8 0x0000563f06c49d89 in pgtk_handle_selection_clear (event=<optimized
> out>) at pgtkselect.c:742
> selection = <optimized out>
> changed_owner_time = 0
> selection_symbol = <optimized out>
> local_selection_data = <optimized out>
> local_selection_time = <optimized out>
> dpyinfo = 0x90c1b80
> Vselection_alist = <optimized out>
Sadly, it seems that most of the relevant local variables have been
optimized out. Would you please run (in this frame):
(gdb) *event
(gdb) p *event->selection
Thanks.
next prev parent reply other threads:[~2023-05-21 0:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 18:52 bug#63614: 29.0.91; PGTK Emacs crashes after clearing the clipboard Leonardo Hernández via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-21 4:30 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 5:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 6:42 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-24 6:37 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-24 6:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 5:34 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 6:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 6:48 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 10:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 20:27 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-26 0:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-26 2:01 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-26 3:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-26 3:29 ` leohdz172--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87lehi1p7x.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=63614@debbugs.gnu.org \
--cc=leohdz172@proton.me \
--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).