From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16776 invoked by alias); 16 Mar 2011 10:13:53 -0000 Received: (qmail 16765 invoked by uid 22791); 16 Mar 2011 10:13:52 -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; Wed, 16 Mar 2011 10:13:47 +0000 Received: (qmail 15142 invoked from network); 16 Mar 2011 10:13:45 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 16 Mar 2011 10:13:45 -0000 From: Pedro Alves To: Jan Kratochvil Subject: Re: [patch] [gdbserver] Fix multi-GB error log files Date: Wed, 16 Mar 2011 11:44: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> <201103151941.16708.pedro@codesourcery.com> <20110316093228.GA27281@host1.jankratochvil.net> In-Reply-To: <20110316093228.GA27281@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103161013.41848.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/msg00837.txt.bz2 On Wednesday 16 March 2011 09:32:28, Jan Kratochvil wrote: > Hi Pedro, > > if the only concern is the late release cycle phase it can wait. When it > waited so many ears I do not find a need to provide a temporary testsuite-only > fix just to fix the 7.3 gdbserver testsuite. > > So the question is whether do you want to fix the racey user-facing behavior > of gdbserver or not, independent of the GDB release cycle. Yes, I'm willing to give that a try. I do think your patch solves it in a way that makes sense: without --once, the default, we leave the socket open; with --once, we release it as soon as possible, so the user can still open several debug sessions with the same port, if he's okay with not being able to reconnect back to the same gdbserver. -- Pedro Alves