public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29854] ^C should interrupt synchronous wait on cooked index completion Date: Thu, 09 Feb 2023 14:35:15 +0000 [thread overview] Message-ID: <bug-29854-4717-7j0YPylbDk@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29854-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29854 --- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=307733cc0fa864fcb92f4c308a0a27d17552df37 commit 307733cc0fa864fcb92f4c308a0a27d17552df37 Author: Tom Tromey <tromey@adacore.com> Date: Tue Dec 6 08:05:28 2022 -0700 Let user C-c when waiting for DWARF index finalization In PR gdb/29854, Simon pointed out that it would be good to be able to use C-c when the DWARF cooked index is waiting for finalization. The idea here is to be able to interrupt a command like "break" -- not to stop the finalization process itself, which runs in a worker thread. This patch implements this idea, by changing the index wait functions to, by default, allow a quit. Polling is done, because there doesn't seem to be a better way to interrupt a wait on a std::future. For v2, I realized that the thread compatibility code in thread-pool.h also needed an update. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29854 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-09 14:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-05 19:43 [Bug gdb/29854] New: " simon.marchi at polymtl dot ca 2022-12-05 23:34 ` [Bug gdb/29854] " tromey at sourceware dot org 2022-12-06 0:00 ` tromey at sourceware dot org 2022-12-06 2:38 ` simark at simark dot ca 2022-12-06 15:05 ` tromey at sourceware dot org 2022-12-06 15:34 ` simark at simark dot ca 2022-12-06 19:09 ` tromey at sourceware dot org 2022-12-06 19:29 ` tromey at sourceware dot org 2022-12-25 19:55 ` tromey at sourceware dot org 2023-02-09 14:35 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-09 14:35 ` 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-29854-4717-7j0YPylbDk@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: linkBe 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).