public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "raheel.hameed at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16591] New: Feature: Be able to Freeze or Thaw individual threads
Date: Sat, 15 Feb 2014 00:00:00 -0000 [thread overview]
Message-ID: <bug-16591-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=16591
Bug ID: 16591
Summary: Feature: Be able to Freeze or Thaw individual threads
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: raheel.hameed at gmail dot com
There should be a command to Freeze a particular thread from execution i.e. the
thread would suspend execution.
Similarly, there should be a command to Thaw a frozen thread so it would resume
the execution.
This feature can be very useful to induce race conditions during multithreads
debugging.
The thread information list (info threads command) should display a single byte
column that would tell if the thread is currently frozen.
As an FYI, in Windows world Visual Studio supports this useful feature. It can
be used by Right clicking on a thread in Threads window and choose Freeze or
Thaw option.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-02-15 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 0:00 raheel.hameed at gmail dot com [this message]
2014-02-15 0:01 ` [Bug gdb/16591] " raheel.hameed at gmail dot com
2022-04-08 1:51 ` 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-16591-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: link
Be 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).