public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "epasveer at att dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/31090] "mi" equivalent of "(gdb) kill"
Date: Tue, 28 Nov 2023 15:27:35 +0000	[thread overview]
Message-ID: <bug-31090-4717-jL8v6ydYL7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31090-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31090

--- Comment #2 from Ernie Pasveer <epasveer at att dot net> ---
Yes, the CLI "kill" command does work. However, it's not "mi" friendly for
frontend use. eg: there's no "^done" message afterwards.

I'll attempt to implement it and submit a patch, as per the documents.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-11-28 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  0:03 [Bug mi/31090] New: " epasveer at att dot net
2023-11-28  1:19 ` [Bug mi/31090] " tromey at sourceware dot org
2023-11-28 15:27 ` epasveer at att dot net [this message]

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=bug-31090-4717-jL8v6ydYL7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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. 
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).