From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31026 invoked by alias); 15 Mar 2011 18:36:12 -0000 Received: (qmail 30946 invoked by uid 22791); 15 Mar 2011 18:36:11 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Mar 2011 18:36:08 +0000 Received: (qmail 6800 invoked from network); 15 Mar 2011 18:36:06 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 Mar 2011 18:36:06 -0000 From: Pedro Alves To: Jan Kratochvil Subject: Re: [patch] [gdbserver] Fix multi-GB error log files Date: Tue, 15 Mar 2011 18:48:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-27-generic; KDE/4.6.1; x86_64; ; ) Cc: gdb-patches@sourceware.org, Daniel Jacobowitz References: <20110306115536.GA31532@host1.jankratochvil.net> <201103151742.56925.pedro@codesourcery.com> <20110315180423.GA28968@host1.jankratochvil.net> In-Reply-To: <20110315180423.GA28968@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103151836.02729.pedro@codesourcery.com> X-IsSubscribed: yes 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 X-SW-Source: 2011-03/txt/msg00806.txt.bz2 On Tuesday 15 March 2011 18:04:23, Jan Kratochvil wrote: > On Tue, 15 Mar 2011 18:42:56 +0100, Pedro Alves wrote: > > I'm worried about whether this breaks use > > cases. E.g., as is, you can spawn several instances of > > gdbserver + connect, while only needing to open one port in > > your firewall. Or perhaps IDEs are relying on that when > > spawning the second (and nth) connections to the same > > board (while leaving the previous sessions still running). > > In such case we can make --once default: I don't think that's a good idea. When the user does "disconnect" (, or gdb crashes), we don't want gdbserver to exit. > > On Sun, 06 Mar 2011 12:55:36 +0100, Jan Kratochvil wrote: > # Also when --once is already introduced it could be made default (that is > # introduce an option "--permanent" to keep the current behavior). But this > # changes the behavior of gdbserver which the users may be used to. > > It was not made the default just for backward compatibility which you state > got broken anyway. I'm confused. Backwards compatibility would be broken by the listen socket change. But that socket change looked orthogonal to the --once stuff? Won't either of the changes fix the problem? -- Pedro Alves