This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/18127] New: threads spawned by infcall end up stuck in "running" state
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 14 Mar 2015 15:58:12 +0000
- Subject: [Bug threads/18127] New: threads spawned by infcall end up stuck in "running" state
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18127
Bug ID: 18127
Summary: threads spawned by infcall end up stuck in "running"
state
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: threads
Assignee: unassigned at sourceware dot org
Reporter: palves at redhat dot com
Ref: https://sourceware.org/ml/gdb/2015-03/msg00033.html
Calling a function that spawns new threads results in the new threads getting
stuck in "running" state.
On GNU/Linux, and a trivial program that has:
~~~
void
start_thread (void)
{
pthread_t thread;
pthread_create (&thread, NULL, thread_function, NULL);
}
~~~
calling that from GDB results in:
(gdb) p start_thread ()
[New Thread 0x7ffff7fc1700 (LWP 9903)]
$1 = void
(gdb) info threads
Id Target Id Frame
2 Thread 0x7ffff7fc1700 (LWP 9903) "start-thread-in" (running)
* 1 Thread 0x7ffff7fc2740 (LWP 9899) "start-thread-in" main () at
start-thread-infcall.c:35
--
You are receiving this mail because:
You are on the CC list for the bug.