unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Géza <geza.herman@gmail.com>
Cc: 54667@debbugs.gnu.org
Subject: bug#54667: 29.0.50; posix_spawn breaks emacs-gdb
Date: Fri, 01 Apr 2022 14:16:02 +0200	[thread overview]
Message-ID: <87fsmx80e5.fsf@gmail.com> (raw)
In-Reply-To: <f26aa6b4-654d-dbba-4e6f-4c71a03e3d5a@gmail.com>

>>>>> On Fri, 1 Apr 2022 12:51:43 +0200, Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com> said:

    Herman> There's a gdb frontend: https://github.com/weirdNox/emacs-gdb
    Herman> With the emacs commit "a60053f836 Use posix_spawn if possible.",
    Herman> emacs-gdb doesn't work properly: when starting an executable, gdb says
    Herman> that it's running, but in reality, it doesn't start. The process
    Herman> itself is started, gdb attaches to it, but the process still not run
    Herman> for some reason.

    Herman> You can reproduce this:
    Herman> 1. install emacs-gdb
    Herman> 2. M-x gdb-executable, enter any executable, like "/bin/ls". emacs-gdb
    Herman> should open a new frame.
    Herman> 3. Then press f5 (this executes gdb-run-or-continue), this should
    Herman> start the process in gdb.

    Herman> Before the mentioned commit, this worked, and "ls" was run
    Herman> properly. But with this commit, "ls" isn't started.

    Herman> I checked this with a recent master
    Herman> (bd5d136777ef30f36807c7e690413846ed38fce1), and still happens. Adding

    Herman> #undef USABLE_POSIX_SPAWN
    Herman> #define USABLE_POSIX_SPAWN 0

    Herman> to callproc.c at line 49 fixes the issue.

Thereʼs a patch from Jürgen Hötzel in <86o82mvybj.fsf@hoetzel.info> on
emacs-devel that should fix it (I haven't had a chance to fully test
it).

Robert
-- 





  reply	other threads:[~2022-04-01 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 10:51 bug#54667: 29.0.50; posix_spawn breaks emacs-gdb Herman, Géza
2022-04-01 12:16 ` Robert Pluim [this message]
2022-04-01 13:29   ` Herman, Géza
2022-04-01 14:44     ` Robert Pluim
2022-04-04 14:11       ` Robert Pluim
2022-04-17 18:53       ` Philipp Stephani

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=87fsmx80e5.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=54667@debbugs.gnu.org \
    --cc=geza.herman@gmail.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).