public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at ericsson dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/18600] New: After forking and threads spawning, gdb leaves newly created threads stopped
Date: Thu, 25 Jun 2015 17:08:00 -0000 [thread overview]
Message-ID: <bug-18600-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18600
Bug ID: 18600
Summary: After forking and threads spawning, gdb leaves newly
created threads stopped
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: threads
Assignee: unassigned at sourceware dot org
Reporter: simon.marchi at ericsson dot com
Target Milestone: ---
When a program forks and the fork childs start threads, some newly created
threads are left stopped by gdb. It's easy to reproduce with the following
example:
https://github.com/simark/gdb-fork-threads-test/
It worked with gdb 7.9, I bisected it and found that this commit introduces the
regression.
commit 2db9a4275ceada4aad3443dc157b96dd2e23afc0
Author: Pedro Alves <palves@redhat.com>
Date: Fri Feb 20 20:21:59 2015 +0000
GNU/Linux: Stop using libthread_db/td_ta_thr_iter
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-06-25 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 17:08 simon.marchi at ericsson dot com [this message]
2015-06-25 17:08 ` [Bug threads/18600] " simon.marchi at ericsson dot com
2015-07-07 22:11 ` simon.marchi at ericsson dot com
2015-07-30 17:55 ` cvs-commit at gcc dot gnu.org
2015-07-30 17:55 ` cvs-commit at gcc dot gnu.org
2015-07-30 18:05 ` cvs-commit at gcc dot gnu.org
2015-07-30 18:05 ` cvs-commit at gcc dot gnu.org
2015-07-30 18:26 ` palves at redhat dot com
2015-08-06 14:02 ` cvs-commit at gcc dot gnu.org
2015-08-06 14:03 ` cvs-commit at gcc dot gnu.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-18600-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).