From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27635 invoked by alias); 25 Oct 2008 02:00:45 -0000 Received: (qmail 27608 invoked by uid 22791); 25 Oct 2008 02:00:44 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 25 Oct 2008 02:00:09 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0B7112A964C; Fri, 24 Oct 2008 22:00:07 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GWcEWeq1NTu0; Fri, 24 Oct 2008 22:00:06 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C8F9B2A964B; Fri, 24 Oct 2008 22:00:06 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id A68D9E7ACD; Fri, 24 Oct 2008 19:00:01 -0700 (PDT) Date: Sat, 25 Oct 2008 02:00:00 -0000 From: Joel Brobecker To: Hilfinger@CS.Berkeley.EDU Cc: gdb-patches@sourceware.org Subject: Re: [RFA/RFC] new setting against auto-answer? (because "input not from terminal") Message-ID: <20081025020001.GD29998@adacore.com> References: <20081025010445.GC29038@adacore.com> <200810250140.m9P1e1ho011456@tully.CS.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200810250140.m9P1e1ho011456@tully.CS.Berkeley.EDU> User-Agent: Mutt/1.4.2.2i 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: 2008-10/txt/msg00629.txt.bz2 > > I propose a new "set/show interactive-mode (auto|on|off)" command > > to allow the user to override what GDB detects. By default, GDB > > still probes stdin and determines from there what mode should be > > used. But if the user knows what he's doing, he can force it in > > situations where GDB's default behavior is less useful. > > If the behavior of GDB on other OS's is OK, shouldn't this be a > configuration parameter of some sort, preferably set automatically by > configure? I don't think it would be a good idea to make it a configure parameter. If you freeze the setting to interactive mode at configure time, then the debugger is stuck in that mode, even when stdin is a real pipe: cat commands | gdb -- Joel