From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24154 invoked by alias); 20 Jan 2008 01:01:43 -0000 Received: (qmail 24133 invoked by uid 22791); 20 Jan 2008 01:01:42 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Jan 2008 01:01:23 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 489E798020; Sun, 20 Jan 2008 01:01:21 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 24EC798009; Sun, 20 Jan 2008 01:01:21 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JGOYp-00076N-AM; Sat, 19 Jan 2008 20:01:19 -0500 Date: Sun, 20 Jan 2008 01:01:00 -0000 From: Daniel Jacobowitz To: Bill Gatliff Cc: gdb@sourceware.org Subject: Re: Gdbserver from inetd? Message-ID: <20080120010119.GA27135@caradoc.them.org> Mail-Followup-To: Bill Gatliff , gdb@sourceware.org References: <47922461.7040101@billgatliff.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47922461.7040101@billgatliff.com> User-Agent: Mutt/1.5.17 (2007-12-11) 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-01/txt/msg00194.txt.bz2 On Sat, Jan 19, 2008 at 10:25:05AM -0600, Bill Gatliff wrote: > Guys: > > > I see in the archives some occasional comments about running gdbserver > from inetd. > > I would REALLY love to be able to do that! Is it supported by the > current gdbserver? If so, how do I take advantage of it? No. > If not, is it really just a matter of hooking gdbserver to stdio instead > of the existing options? (Seems too easy to be true). Maybe. I haven't written an inetd-capable application in a decade. You might have trouble finding something to do with the debugee's output. -- Daniel Jacobowitz CodeSourcery