unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 55672@debbugs.gnu.org
Subject: bug#55672: 29.0.50; Emacs crashes when calling start-process-shell-command xdg-open with process-connection-type set to nil
Date: Fri, 27 May 2022 15:45:59 +0800	[thread overview]
Message-ID: <87h75bh0zs.fsf@localhost> (raw)
In-Reply-To: <87ilprihg0.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>> I am experiencing Emacs crashes/flickering on Linux with the
>> following:
>
> Then please show a backtrace from such a crash generated by gdb.

After compiling Emacs with the following configure flags:
./configure --enable-checking='yes,glyphs'
--enable-check-lisp-object-type CFLAGS='-O0 -g3'
--without-compress-install --without-hesiod --without-pop
--with-file-notification=inotify --with-pdumper --enable-acl --with-dbus
--with-modules --without-gameuser --with-libgmp --without-gpm
--with-native-compilation --with-json --without-kerberos
--without-kerberos5 --without-lcms2 --with-xml2 --without-mailutils
--with-selinux --without-sqlite3 --with-gnutls --without-libsystemd
--with-threads --with-wide-int --with-zlib --with-sound=oss --with-x
--without-pgtk --without-ns --without-gconf --without-gsettings
--without-toolkit-scroll-bars --with-xpm --with-xft --with-cairo
--with-harfbuzz --without-libotf --without-m17n-flt --with-x-toolkit=no
--with-gif --with-jpeg --with-png --with-rsvg --with-tiff --without-webp
--with-imagemagick --with-dumping=pdumper

I got the following backtrace after waiting for deferred native-comp to
finish and executing
(let ((process-connection-type nil))
  (start-process-shell-command "1" nil "xdg-open ~/.bashrc"))
multiple times in scratch buffer:

> gdb --args ./emacs -Q -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 -l /home/yantar92/bug.el
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff049d640 (LWP 17839)]
[Detaching after vfork from child process 17907] <- flickering
[Detaching after vfork from child process 18197] <- flickering
[Detaching after vfork from child process 18326] <- flickering
[Detaching after vfork from child process 18419] <- flickering
[Detaching after vfork from child process 18542] <- flickering
[Detaching after vfork from child process 18654]

Thread 1 "emacs" hit Breakpoint 2, x_error_quitter (display=0x555559323390, event=0x7fffffffa210) at xterm.c:21573
21573	{
(gdb) 
(gdb) 
quit
A debugging session is active.

	Inferior 1 [process 17832] will be killed.

Quit anyway? (y or n) y

Best,
Ihor





  reply	other threads:[~2022-05-27  7:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  6:24 bug#55672: 29.0.50; Emacs crashes when calling start-process-shell-command xdg-open with process-connection-type set to nil Ihor Radchenko
2022-05-27  7:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  7:45   ` Ihor Radchenko [this message]
2022-05-27  7:49     ` Ihor Radchenko
2022-05-27  8:03     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  8:44       ` Ihor Radchenko
2022-05-27  9:01         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  9:15           ` Ihor Radchenko
2022-05-27  9:31             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  9:48               ` Ihor Radchenko
2022-05-27  9:57                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:04                   ` Ihor Radchenko
2022-05-27 10:08                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:13                       ` Ihor Radchenko
2022-05-27 10:24                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:28     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:35       ` Ihor Radchenko
2022-05-27 11:56         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 12:06           ` Ihor Radchenko
2022-05-27 13:11         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 13:37           ` Ihor Radchenko
2022-05-27 13:46             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 13:48               ` Ihor Radchenko
2022-07-24  5:48             ` Ihor Radchenko

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=87h75bh0zs.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=55672@debbugs.gnu.org \
    --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).