This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] remote-sim add call to init_thread_list
- From: "Andrew Burgess" <aburgess at broadcom dot com>
- To: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 11 Oct 2012 22:27:03 +0100
- Subject: Re: [PATCH] remote-sim add call to init_thread_list
- References: <506C2A17.8060000@broadcom.com> <5076D840.9010904@redhat.com>
On 11/10/2012 3:31 PM, Pedro Alves wrote:
> On 10/03/2012 01:05 PM, Andrew Burgess wrote:
>> When running using a basic exec style target (on linux) I see the following behaviour:
>>
>>> gdb ./test-program
>> (gdb) start
>> (gdb) info threads
>> Id Target Id Frame
>> * 1 process 12285 main () at hello.c:5
>> (gdb) start
>> The program being debugged has been started already.
>> Start it from the beginning? (y or n) y
>>
>> (gdb) info threads
>> Id Target Id Frame
>> * 1 process 16295 main () at hello.c:5
>>
>> ## END ##
>>
>> Notice that the thread ID remains as 1 after the restart. This is due to the call to init_thread_list in gdb/fork-child.c:fork_inferior.
>>
>> Currently, when using a simulator target, the ID will increment on each restart.
>>
>> The patch below adds a similar call to init_thread_list to remote-sim.c:create_inferior so the simulator behaviour will match the native exec style target behaviour.
>>
>> OK to apply?
>
> OK.
Committed.
Thanks for the review.
Andrew