From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [Detaching after vfork from child process NNNNN]
Date: Wed, 03 Jan 2024 14:53:00 +0200 [thread overview]
Message-ID: <838r56zihf.fsf@gnu.org> (raw)
In-Reply-To: <E1rKsdT-0003HW-6E@fencepost.gnu.org> (message from Richard Stallman on Tue, 02 Jan 2024 23:13:43 -0500)
> From: Richard Stallman <rms@gnu.org>
> Date: Tue, 02 Jan 2024 23:13:43 -0500
>
> I just started using the latest master to edit with, and actions that
> create subprocesses often display
>
> [Detaching after vfork from child process NNNNN]
>
> on the tty which is Emacs's output device. This is quite invonenient
> when doing normal editing with Emacs running under GDB.
This is a message from GDB.
> I turned those messages off by adding the line
>
> set print inferior-events off
>
> to src/.gdbinit.
>
> Is it really right for the printing of those events to be enabled by
> default?
IMO yes, since inferior-events include process start and exit, and
those events are important in general when debugging.
> How about adding that line to .gdbinit by default,
> with a comment explaining what would result form deleting it?
I don't think it's a good idea to do that for everyone here. I, for
one, want to see these events announced. You can, of course, add this
to your personal ~/.gdbinit.
It might also be a good idea to extend the "set detach-on-fork"
command in GDB to allow more fine-grained control, including shutting
down the announcement of the detachment. If you think this is a good
idea, I suggest to talk to the GDB developers or maybe even suggest a
patch to them.
next prev parent reply other threads:[~2024-01-03 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 4:13 [Detaching after vfork from child process NNNNN] Richard Stallman
2024-01-03 12:53 ` Eli Zaretskii [this message]
2024-01-11 4:05 ` Richard Stallman
2024-01-11 6:39 ` Eli Zaretskii
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=838r56zihf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).