[PATCH 10/18] Remote thread create/exit events
Pedro Alves
palves@redhat.com
Mon Nov 23 15:41:00 GMT 2015
On 10/26/2015 01:54 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
> Hi Pedro,
>
>> @@ -6417,6 +6425,11 @@ Packet: '%s'\n"),
>> one used by the original program. */
>> skipregs = 1;
>> }
>> + else if (strprefix (p, p1, "create"))
>> + {
>> + event->ws.kind = TARGET_WAITKIND_THREAD_CREATED;
>> + p = skip_to_semicolon (p1 + 1);
>> + }
>> else
>> {
>> ULONGEST pnum;
>
> Looks you add thread create/exit events on current stop notification.
> I am wondering why don't we add a new notification for thread
> create/exit. It should straightforward to add a new notification under
> current remote notification infrastructure.
Actually, TARGET_WAITKIND_THREAD_CREATED is really a stop, just like
TARGET_WAITKIND_FORKED, etc. That is, when it is reported, the thread
is stopped at its entry point.
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list