This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 10/18] Remote thread create/exit events
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 26 Oct 2015 13:54:34 +0000
- Subject: Re: [PATCH 10/18] Remote thread create/exit events
- Authentication-results: sourceware.org; auth=none
- References: <1444836486-25679-1-git-send-email-palves at redhat dot com> <1444836486-25679-11-git-send-email-palves at redhat dot com>
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.
--
Yao (éå)