From: Akira Kyle <akira@akirakyle.com>
To: 53013@debbugs.gnu.org
Subject: bug#53013: 29.0.50; xwidget-webkit: SIGCHLD not being caught after xwidget-webkit buffer killed
Date: Tue, 04 Jan 2022 14:10:05 -0700 [thread overview]
Message-ID: <86bl0r6wcy.fsf@akirakyle.com> (raw)
In GNU Emacs 29.0.50 (build 1, aarch64-unknown-linux-gnu, GTK+ Version 3.24.30, cairo version 1.16.0)
Repository revision: ab5ee3e29e916d4009b301841e9780aad564a6a0
Repository branch: master
System Description: NixOS 22.05 (Quokka)
Configured using:
'configure
--prefix=/nix/store/0fiqa453abl4c1c28g0baqs9s274s7ff-emacs-pgtkgcc-20220103.0
--disable-build-details --with-modules --with-x-toolkit=gtk3
--with-cairo --with-xwidgets --with-native-compilation --with-pgtk'
Also tested on debian under GNOME (wayland) with the same configuration.
Steps to reproduce in emacs -Q:
- M-x xwidget-webkit-browse-url RET http://xkcd.com RET
- C-x k RET
- M-: (start-process "my-process" "foo" "echo" "hi")
No "Process my-process finished" line appears in buffer "foo" indicating
that emacs didn't catch SIGCHLD.
I suspect that a call to catch_child_signal might also be needed in
kill_xwidget so emacs reinstalls its signal handler.
next reply other threads:[~2022-01-04 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 21:10 Akira Kyle [this message]
2022-01-05 2:40 ` bug#53013: 29.0.50; xwidget-webkit: SIGCHLD not being caught after xwidget-webkit buffer killed Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 5:04 ` Akira Kyle
2022-01-07 4:21 ` Richard Stallman
2022-01-07 4:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-08 3:58 ` Richard Stallman
2022-01-08 4:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 3:54 ` Richard Stallman
2022-01-14 8:19 ` Lars Ingebrigtsen
2022-01-14 8:20 ` Lars Ingebrigtsen
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=86bl0r6wcy.fsf@akirakyle.com \
--to=akira@akirakyle.com \
--cc=53013@debbugs.gnu.org \
/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).