public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/11580] scheduler-locking breaks re-runs Date: Thu, 13 May 2010 17:17:00 -0000 [thread overview] Message-ID: <20100513171741.15072.qmail@sourceware.org> (raw) In-Reply-To: <20100507183730.11580.k04jg02@gmail.com> ------- Additional Comments From pedro at codesourcery dot com 2010-05-13 17:17 ------- Yes, though command proliferation whenever we need a new flag, is probably not that great, and is limited, e.g., expression evaluation (infcalls) may need locking as well (for p, x, and others). HPD's (and TotalView's) ptsets handle that nicely, IMO, with syntax that allows scoping a command to a thread process, or thread group. We have some work in that direction implemented in the old multiprocess branch in cvs, in the form of itsets (inferior thread sets). Unfortunately, that never made it to completion. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11580 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-05-13 17:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-07 18:37 [Bug threads/11580] New: " k04jg02 at gmail dot com 2010-05-12 17:36 ` [Bug threads/11580] " msnyder at sonic dot net 2010-05-12 17:52 ` k04jg02 at gmail dot com 2010-05-12 18:04 ` pedro at codesourcery dot com 2010-05-13 16:46 ` dje at google dot com 2010-05-13 17:12 ` pedro at codesourcery dot com 2010-05-13 17:17 ` pedro at codesourcery dot com [this message] 2010-05-13 17:21 ` pedro at codesourcery dot com [not found] <bug-11580-4717@http.sourceware.org/bugzilla/> 2022-11-29 20:18 ` 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=20100513171741.15072.qmail@sourceware.org \ --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).