From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3466 invoked by alias); 18 Jul 2008 21:41:39 -0000 Received: (qmail 3454 invoked by uid 22791); 18 Jul 2008 21:41:39 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jul 2008 21:41:21 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id m6ILfCwe001048; Fri, 18 Jul 2008 23:41:13 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id m6ILfBcf014252; Fri, 18 Jul 2008 23:41:12 +0200 (CEST) Date: Fri, 18 Jul 2008 22:13:00 -0000 Message-Id: <200807182141.m6ILfBcf014252@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: stanshebs@earthlink.net CC: gdb@sourceware.org In-reply-to: <4880FFA8.3080600@earthlink.net> (message from Stan Shebs on Fri, 18 Jul 2008 13:40:08 -0700) Subject: Re: Towards multiprocess GDB References: <4880FFA8.3080600@earthlink.net> 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/msg00214.txt.bz2 > 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? 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'd simply fire up two (or more) xterms and debug the processes seperately. One thing that could be useful though for that scenario is the ability to hand of processes between gdb instances upon fork/exec. I suppose multiprocess debugging makes somewhat more sense in a GUI-based IDE environment. But running multiple instances of gdb should work just as well in that case. Adding a "multiprocess" capability to GDB is almost certainly going to add significant complexity. So there should be a good motivation for it.