From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14336 invoked by alias); 11 Jun 2008 16:43:48 -0000 Received: (qmail 14327 invoked by uid 22791); 11 Jun 2008 16:43:48 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Jun 2008 16:43:27 +0000 Received: (qmail 755 invoked from network); 11 Jun 2008 16:43:25 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Jun 2008 16:43:25 -0000 From: Vladimir Prus To: Pawel Piech , gdb@sources.redhat.com Subject: Re: Multiprocess MI extensions Date: Wed, 11 Jun 2008 16:43:00 -0000 User-Agent: KMail/1.9.9 References: <200806102323.48023.vladimir@codesourcery.com> <484FFFC3.5000806@windriver.com> In-Reply-To: <484FFFC3.5000806@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806112043.29337.vladimir@codesourcery.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00097.txt.bz2 On Wednesday 11 June 2008 20:39:31 you wrote: > > Just to make sure we're on the same page -- if we use one notification for everything, > > it will either have a 'thread' field -- when a thread is created/exited, or 'thread-group' > > field, when process is created/exited. Is that OK? > > > > > Yes, that's fine. A more forward looking alternative would be to have a > consistent id field and a type field which would indicate whether it's a > group, thread, etc. Hopefully, the thread-group concept of so general that we'll only even need to introduce new types of thread groups. IOW, instead of having id and type in all notifications, we'll have id pointing at thread group, and the type will be part of thread group. - Volodya