public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29854] New: ^C should interrupt synchronous wait on cooked index completion Date: Mon, 05 Dec 2022 19:43:41 +0000 [thread overview] Message-ID: <bug-29854-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29854 Bug ID: 29854 Summary: ^C should interrupt synchronous wait on cooked index completion Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at polymtl dot ca Target Milestone: --- Using commit 09a5d200e6166522e0d0a9276bd6b2227ac5ace1, I do: $ ./gdb -nx -q --data-directory=data-directory testsuite/outputs/gdb.gdb/selftest/xgdb Reading symbols from testsuite/outputs/gdb.gdb/selftest/xgdb... (gdb) b captured_main ^C Creating the breakpoint takes some time, doing ^C does nothing. Attaching to GDB, I understood that it's because the main thread is waiting on the `table->wait ()` call, waiting for worker threads to finish building the cooked indices. Not sure how we can do it, but it would be nice for ^C to interrupt that table->wait call and generate a gdb_exception_quit. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-05 19:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-05 19:43 simon.marchi at polymtl dot ca [this message] 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 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@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).