public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17130] Quit regression on targets that don't have job_control / terminal switching (expect signal SIGINT when the program is resumed) Date: Tue, 08 Jul 2014 16:31:00 -0000 [thread overview] Message-ID: <bug-17130-4717-zOb426vWhX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17130-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17130 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #1 from Tom Tromey <tromey at redhat dot com> --- There's a case in sol-thread.c: if (beneath->to_find_new_threads != NULL) beneath->to_find_new_threads (beneath); No bug here, just the test can be deleted. There are also a few to investigate in record: ./record-btrace.c: if (ops->to_xfer_partial != NULL) ./record-btrace.c: if (t->to_fetch_registers != NULL) ./record-btrace.c: if (t->to_store_registers != NULL) ./record-btrace.c: if (t->to_prepare_to_store != NULL) ./record-btrace.c: if (ops->to_resume != NULL) ./record-btrace.c: if (ops->to_wait != NULL) ./record-btrace.c: if (ops->to_find_new_threads != NULL) ./record-btrace.c: if (ops->to_thread_alive != NULL) Some of those are probably not delegated (I didn't check yet), but some are. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-08 16:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-08 15:54 [Bug gdb/17130] New: " palves at redhat dot com 2014-07-08 16:31 ` tromey at redhat dot com [this message] 2014-07-08 17:33 ` [Bug gdb/17130] " palves at redhat dot com 2014-07-11 14:00 ` tromey at redhat dot com 2014-07-18 15:56 ` cvs-commit at gcc dot gnu.org 2014-07-18 15:57 ` tromey at redhat dot com 2014-07-25 8:48 ` palves at redhat dot com
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-17130-4717-zOb426vWhX@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).