Inadvertently run inferior threads

[Eli Zaretskii]

> Date: Sat, 14 Mar 2015 15:35:56 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: gdb@sourceware.org
> 
> > In that case, the cause of it getting out of sync is the new thread
> > that was started (probably by Windows)?
> 
> Calling a function that ends up starting new threads should
> work OK, but indeed that seems to be broken...

Yes, but in my case the called function didn't really start any
threads...

That said, thanks for the info, it could very well be relevant.

> (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

What does "start-thread-in" signify in this display?