bug#70072: 29.3; Emacs-PGTK crashes upon kill-region or kill-ring-save

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 29 Mar 2024 15:43:52 +0100 (CET)
> From:  "Abraham S.A.H." via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> ## System Information:
> 
> * Kernel: 6.8.2-2
> * DE: Gnome 46.0
> * WM: Mutter (Wayland)
> * gnome-shell: 46.0
> * wayland: 1.22.0
> * mutter: 46.0
> * wl-clipboard: 2.2.1
> * weston: 13.0.0
> * sway: 1.9-e93da93
> * emacs package: emacs-wayland 29.3-1.1 (archlinux)
> 
> ## Steps to reproduce the issue under Gnome:
> 
> 1. Invoke `emacs -Q` in any terminal emulator to start Emacs along with
>    its GUI frame.
> 2. Mark/highlight some area of text with your mouse pointer. OR use
>    C-Space and keyboard movement shortcuts to do the same.
> 3. Use `C-w` or `M-w` to kill or kill-save the marked text.
> 5. Emacs crashes.
> 
> NOTE1: The problem is reproducible both when marking with mouse cursor
>        or when marking with keyboard shortcuts.
> NOTE2: Using `kill-region` or `kill-ring-save` commands results in the
>        same state.
> NOTE3: Copying or cutting text outside Emacs and yanking inside Emacs
>        works without any problem.
> 
> ## State of the issue under Sway:
> 
> Just Killing doesn't make Emacs to crash, but then trying to paste it
> into other applications make Emacs to crash.
> 
> ## State of the issue under Weston:
> 
> Copying and cutting outside of Emacs and yanking into Emacs works
> without issues.  Killing inside Emacs doesn't make it to crash, but 
> it also doesn't paste inside other applications, and makes the current
> clipboard to get empty.
> 
> ## Workaround:
> Set variable `select-enable-clipboard` to `nil`.
> 
> ## Terminal log of Emacs after crash:
> 
> ~~~~~~~~~~ Start of the log
> Fatal error 11: Segmentation fault
> Backtrace:
> 
> emacs(+0x16bc62)[0x5f8b0fcddc62]
> emacs(+0x20243)[0x5f8b0fb92243]
> emacs(+0x21d44)[0x5f8b0fb93d44]
> /usr/lib/libc.so.6(+0x41b30)[0x735b53041b30]

Thank you for your report, but these backtraces can only be
interpreted on your system.  So either convert them to human-readable
lists of file names, line numbers, and function names as described in
the node "Crashing" of the Emacs user manual, or run Emacs from GDB,
and when Emacs crashes, type "bt" at the GDB prompt and post the
backtrace produced by GDB.

> fish: Job 1, 'emacs --debug-init' terminated by signal SIGSEGV (Address
> boundary error)

This says you invoked Emacs with --debug-init, not with -Q.  Which one
is correct?