From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115688 invoked by alias); 26 Oct 2015 13:54:42 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 115673 invoked by uid 89); 26 Oct 2015 13:54:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-pa0-f50.google.com Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 26 Oct 2015 13:54:41 +0000 Received: by pacfv9 with SMTP id fv9so198025721pac.3 for ; Mon, 26 Oct 2015 06:54:39 -0700 (PDT) X-Received: by 10.66.162.232 with SMTP id yd8mr21931178pab.55.1445867679636; Mon, 26 Oct 2015 06:54:39 -0700 (PDT) Received: from E107787-LIN (gcc2-power8.osuosl.org. [140.211.9.43]) by smtp.gmail.com with ESMTPSA id gv1sm34212806pbc.38.2015.10.26.06.54.37 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 26 Oct 2015 06:54:39 -0700 (PDT) From: Yao Qi To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 10/18] Remote thread create/exit events References: <1444836486-25679-1-git-send-email-palves@redhat.com> <1444836486-25679-11-git-send-email-palves@redhat.com> Date: Mon, 26 Oct 2015 16:50:00 -0000 In-Reply-To: <1444836486-25679-11-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 14 Oct 2015 16:27:58 +0100") Message-ID: <86eggh20rp.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00565.txt.bz2 Pedro Alves writes: Hi Pedro, > @@ -6417,6 +6425,11 @@ Packet: '%s'\n"), > one used by the original program. */ > skipregs =3D 1; > } > + else if (strprefix (p, p1, "create")) > + { > + event->ws.kind =3D TARGET_WAITKIND_THREAD_CREATED; > + p =3D 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. --=20 Yao (=E9=BD=90=E5=B0=A7)