This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Inadvertently run inferior threads
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb at sourceware dot org
- Date: Sat, 14 Mar 2015 18:04:42 +0200
- Subject: Re: Inadvertently run inferior threads
- Authentication-results: sourceware.org; auth=none
- References: <83h9tq3zu3 dot fsf at gnu dot org> <55043A63 dot 6020103 at redhat dot com> <8361a339xd dot fsf at gnu dot org> <5504555C dot 804 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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?