all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Daimrod <daimrod@gmail.com>
Cc: 14597@debbugs.gnu.org
Subject: bug#14597: 24.3.50; Can't stop the program being debugged with gdb-mi
Date: Wed, 09 Sep 2020 15:47:29 +0200	[thread overview]
Message-ID: <87zh5z83ke.fsf@gnus.org> (raw)
In-Reply-To: <87vc52qgho.fsf@tanger.home> (daimrod@gmail.com's message of "Tue, 25 Jun 2013 18:53:23 +0200")

Daimrod <daimrod@gmail.com> writes:

>> `gdb-io-stop' fails to stop the program being debugged when using the
>> GDB/MI interface (M-x gdb run gdb -i=mi). C-c C-z also fails to stop the
>> program. However, no error is reported, it fails silently, without doing
>> anything.

[...]

> Here a workaround, it sends a raw string with "C-z" instead of a signal.
> There is probably a nicer solution but I don't know `gdb-mi.el' and the
> GDB/MI interface enough.
>
> With this, C-c C-z can be used in the gdb-inferior-io buffer to stop the
> program being debugged.

[...]

> -  (stop-process
> -   (get-buffer-process gud-comint-buffer) comint-ptyp))
> +  (process-send-string (get-buffer-process
> +                        (gdb-get-buffer-create 'gdb-inferior-io))
> +                       (kbd "C-z")))

There were unfortunately no comments at the time (seven years ago), but
the code in gdb-mi essentially looks the same to this day.

I'm not very familiar with gdb-mi, though -- does anybody have an
opinion here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-09-09 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  7:59 bug#14597: 24.3.50; Can't stop the program being debugged with gdb-mi Grégoire Jadi
2013-06-25 16:53 ` Daimrod
2020-09-09 13:47   ` Lars Ingebrigtsen [this message]
2020-09-09 15:12     ` Eli Zaretskii
2020-09-10 13:43       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zh5z83ke.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=14597@debbugs.gnu.org \
    --cc=daimrod@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 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.