This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/18600] New: After forking and threads spawning, gdb leaves newly created threads stopped
- From: "simon.marchi at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 25 Jun 2015 17:08:03 +0000
- Subject: [Bug threads/18600] New: After forking and threads spawning, gdb leaves newly created threads stopped
- Auto-submitted: auto-generated
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.