public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30472] DAP "repl" evaluation can make gdb unresponsive
Date: Mon, 06 Nov 2023 21:20:25 +0000	[thread overview]
Message-ID: <bug-30472-4717-iUXLBqvo4J@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30472-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
I was thinking this could be handled by implementing cancellation,
but that will give weird results when used to interrupt an
inferior call.  Like, I suppose it would work, but the inferior
will be left in a somewhat weird state.

Also it seems a little strange to use cancellation to interrupt
a gdb CLI "continue" but not a DAP "continue".

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

  parent reply	other threads:[~2023-11-06 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 15:06 [Bug dap/30472] New: " tromey at sourceware dot org
2023-06-05 15:15 ` [Bug dap/30472] " tromey at sourceware dot org
2023-06-05 15:40 ` tromey at sourceware dot org
2023-07-27 19:43 ` tromey at sourceware dot org
2023-11-06 21:19 ` tromey at sourceware dot org
2023-11-06 21:20 ` tromey at sourceware dot org [this message]
2023-11-07 14:11 ` tromey at sourceware dot org
2023-11-16 20:58 ` tromey at sourceware dot org
2023-12-01 15:41 ` tromey at sourceware dot org
2023-12-11 18:54 ` cvs-commit at gcc dot gnu.org
2023-12-11 18:55 ` tromey at sourceware dot org

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-30472-4717-iUXLBqvo4J@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).