From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7875 invoked by alias); 18 Jul 2008 22:20:06 -0000 Received: (qmail 7862 invoked by uid 22791); 18 Jul 2008 22:20:05 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jul 2008 22:19:43 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw2.br.ibm.com (Postfix) with ESMTP id 4D9C817F4F2 for ; Fri, 18 Jul 2008 19:06:38 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m6IMJhdR426040 for ; Fri, 18 Jul 2008 19:19:43 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m6IMJbMV014706 for ; Fri, 18 Jul 2008 19:19:38 -0300 Received: from [9.8.1.40] ([9.8.1.40]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6IMJb2H014703; Fri, 18 Jul 2008 19:19:37 -0300 Subject: Re: Towards multiprocess GDB From: Thiago Jung Bauermann To: Mark Kettenis Cc: stanshebs@earthlink.net, gdb@sourceware.org In-Reply-To: <200807182141.m6ILfBcf014252@brahms.sibelius.xs4all.nl> References: <4880FFA8.3080600@earthlink.net> <200807182141.m6ILfBcf014252@brahms.sibelius.xs4all.nl> Content-Type: text/plain Date: Fri, 18 Jul 2008 22:28:00 -0000 Message-Id: <1216419576.7240.18.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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-07/txt/msg00216.txt.bz2 On Fri, 2008-07-18 at 23:41 +0200, Mark Kettenis wrote: > > Date: Fri, 18 Jul 2008 13:40:08 -0700 > > From: Stan Shebs > > > > CodeSourcery has a project to add "multiprocess" capability to GDB, > > and with this message I'd like to kick off some discussion of what > > that means and how to make it happen. > > Please remind me, why was this a desirable capability again? One interesting use case I've heard (and which other debuggers support) is debugging both processes involved in a shell pipe command, like: $ producer | consumer So you can say something like "break when variable foo in producer is 2 and variable bar in consumer is 10". I even saw people on the #gdb IRC channel asking for that functionality. > Personally, I can't imagine someone would really want to do this using > the traditional gdb CLI, at least not within a single gdb instance. I think it wouldn't be much different a user experience than debugging a multithreaded application in the CLI. -- []'s Thiago Jung Bauermann Software Engineer IBM Linux Technology Center