From: Stefan Kangas <stefankangas@gmail.com>
To: MEERSMAN Koen <koen.meersman@eurocontrol.int>
Cc: Glenn Morris <rgm@gnu.org>, 14607@debbugs.gnu.org
Subject: bug#14607: 24.3; gdb shell command does not work properly (zsh: command not found: -interpreter-exec)
Date: Wed, 10 Jan 2024 03:16:05 -0800 [thread overview]
Message-ID: <CADwFkmkJSor8dkiSM6Rod80KPayzPtEUh5yOh_5nebR3Yp3ARQ@mail.gmail.com> (raw)
In-Reply-To: <6EC34BA858174241AC9E4AE843A0745801E202C1@FFBRUE003.cfmu.corp.eurocontrol.int> (MEERSMAN Koen's message of "Tue, 18 Jun 2013 12:46:52 +0200")
"MEERSMAN Koen" <koen.meersman@eurocontrol.int> writes:
> Indeed,
>
> I played a bit with gdb-control-commands-regexp and gdb-control-level
> but I was not able to find a quick fix.
> (otherwise I would have added it to the bug report.)
>
> I'll try to teach the developers not to use shell inside gdb, if you do
> it then you can't exit the shell and return to gdb.
>
> Tnx,
>
> Koen
>
>
> -----Original Message-----
> From: Glenn Morris [mailto:rgm@gnu.org]
> Sent: 14 June, 2013 20:41
> To: MEERSMAN Koen
> Cc: 14607@debbugs.gnu.org
> Subject: Re: bug#14607: 24.3; gdb shell command does not work properly
> (zsh: command not found: -interpreter-exec)
>
>
> Adding "shell" to gdb-control-commands-regexp seems to somewhat help,
> but it still isn't right.
That was 10 years ago, so I'm reaching out to see if this is still
relevant on a modern version of Emacs.
If I don't hear back from you within a couple of months, Ill just assume
that this has been fixed and close this bug.
Thanks in advance.
next prev parent reply other threads:[~2024-01-10 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 10:30 bug#14607: 24.3; gdb shell command does not work properly (zsh: command not found: -interpreter-exec) koen.meersman
2013-06-14 18:40 ` Glenn Morris
2013-06-18 10:46 ` MEERSMAN Koen
2024-01-10 11:16 ` Stefan Kangas [this message]
2024-06-09 21:02 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkJSor8dkiSM6Rod80KPayzPtEUh5yOh_5nebR3Yp3ARQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=14607@debbugs.gnu.org \
--cc=koen.meersman@eurocontrol.int \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.