From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C8B983855156; Tue, 6 Dec 2022 00:00:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C8B983855156 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670284809; bh=YQH1Tn9T0UIMjI/50dkqEQUXUStIIZ296gXmFoS2+Kk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CAsA27adouvkC8291Y2tEoeceiQtNBarPcxy/VPskuzPfimWDLaJIkF9ahVYsZcdj pQ2Q9A+9jZ0xVGCvro1IdOS1dvCEKNrJDQ2xemdsYOaGREXrqEFTsijx3JmqNDf90m zwMb7V5NgK3KcBu7r2so71fVQNfT/hI8EGBO9vPE= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29854] ^C should interrupt synchronous wait on cooked index completion Date: Tue, 06 Dec 2022 00:00:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29854 --- Comment #2 from Tom Tromey --- There doesn't seem to be a good way to interrupt future::wait, but I suppose the code could use the wait_for variant and check the quit flag in a loop. I'm also curious why this is taking long enough to notice. --=20 You are receiving this mail because: You are on the CC list for the bug.=