From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philipp Stephani <phst@google.com>, emacs-devel@gnu.org
Subject: Re: Odd gdb problem
Date: Wed, 08 Dec 2021 01:22:57 +0100 [thread overview]
Message-ID: <87ee6o6j32.fsf@gnus.org> (raw)
In-Reply-To: <87mtlcdujt.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 07 Dec 2021 21:33:26 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Perhaps I should just try to bisect the current trunk -- this
> started happening this past week.
Done. And the culprit found at least makes some kind of sense as
something that could break gdb.
Philipp, after this change, I can no longer debug Emacs with gdb on
Debian/bookworm. (It works fine with older gdb versions.)
Do you have any idea what in particular in this change might make gdb
just exit with:
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
a60053f8368e058229721f1bf1567c2b1676b239 is the first bad commit
commit a60053f8368e058229721f1bf1567c2b1676b239
Author: Philipp Stephani <phst@google.com>
Date: Wed Dec 30 14:42:01 2020 +0100
Use posix_spawn if possible.
posix_spawn is less error-prone than vfork + execve, and can make
better use of system-specific enhancements like 'clone' on Linux. Use
it if we don't need to configure a pseudoterminal.
* configure.ac (HAVE_SPAWN_H, HAVE_POSIX_SPAWN)
(HAVE_POSIX_SPAWN_FILE_ACTIONS_ADDCHDIR)
(HAVE_POSIX_SPAWN_FILE_ACTIONS_ADDCHDIR_NP)
(HAVE_POSIX_SPAWNATTR_SETFLAGS, HAVE_DECL_POSIX_SPAWN_SETSID): New
configuration variables.
* src/callproc.c (USABLE_POSIX_SPAWN): New configuration macro.
(emacs_posix_spawn_init_actions)
(emacs_posix_spawn_init_attributes, emacs_posix_spawn_init): New
helper functions.
(emacs_spawn): Use posix_spawn if possible.
configure.ac | 17 ++++++
src/callproc.c | 189 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 205 insertions(+), 1 deletion(-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-08 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 19:43 Odd gdb problem Lars Ingebrigtsen
2021-12-06 19:55 ` Eli Zaretskii
2021-12-06 19:57 ` Lars Ingebrigtsen
2021-12-07 12:48 ` Eli Zaretskii
2021-12-07 20:33 ` Lars Ingebrigtsen
2021-12-08 0:22 ` Lars Ingebrigtsen [this message]
2021-12-08 0:29 ` Lars Ingebrigtsen
2021-12-08 8:13 ` Andreas Schwab
2021-12-08 8:16 ` Lars Ingebrigtsen
2021-12-08 8:34 ` Lars Ingebrigtsen
2021-12-08 8:50 ` Andreas Schwab
2021-12-09 1:10 ` Lars Ingebrigtsen
2021-12-12 11:08 ` 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=87ee6o6j32.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phst@google.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).