bug#55672: 29.0.50; Emacs crashes when calling start-process-shell-command xdg-open with process-connection-type set to nil

[Po Lu]

Ihor Radchenko <yantar92@gmail.com> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>> Please follow the instructions in the file etc/DEBUG on debugging X
>> errors, and show a complete backtrace (type "bt" at the gdb prompt).
>
>> Unless the error happens at a very early stage of display setup, you
>> should run Emacs with "-q -xrm Emacs.synchronous: true", to ensure that
>> X errors are reported immediately after the call that caused them,
>> instead of at the next synchronization point.
>
> Note that it is the first time I am using GDB. I appreciate the
> guidance.
>
> Following your latest instructions:
>
>> gdb --args ./emacs -Q -xrm 'Emacs.synchronous: true' -l ~/bug.el
> GNU gdb (Gentoo 12.1 vanilla) 12.1
> Copyright (C) 2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://bugs.gentoo.org/>.
> Find the GDB manual and other documentation resources online at:
>     <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from ./emacs...
> SIGINT is used by the debugger.
> Are you sure you want to change it? (y or n) [answered Y; input not from 
> terminal]
> DISPLAY = :0
> TERM = xterm-kitty
> Breakpoint 1 at 0x2083b5: file emacs.c, line 420.
> Breakpoint 2 at 0x1cc1d1: file xterm.c, line 21573.
> (gdb) run
> Starting program: /home/yantar92/Git/emacs/src/emacs -Q -xrm 
> Emacs.synchronous:\ true -l /home/yantar92/bug.el

Thanks, but this didn't work.  You must run Emacs with "-q" instead of
"-Q" for X resources passed as command line arguments to take effect.