From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76994 invoked by alias); 10 Feb 2017 16:48:46 -0000 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 Received: (qmail 76971 invoked by uid 89); 10 Feb 2017 16:48:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Feb 2017 16:48:44 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 051DA6AAC2; Fri, 10 Feb 2017 16:48:45 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v1AGmhjQ027035; Fri, 10 Feb 2017 11:48:44 -0500 Subject: Re: [PATCH] Don't send queries to the MI interpreter To: Simon Marchi , gdb-patches@sourceware.org References: <20170210163650.10334-1-simon.marchi@ericsson.com> From: Pedro Alves Message-ID: <89904751-7015-b272-98c1-33e786f7c356@redhat.com> Date: Fri, 10 Feb 2017 16:48:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170210163650.10334-1-simon.marchi@ericsson.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-02/txt/msg00263.txt.bz2 On 02/10/2017 04:36 PM, Simon Marchi wrote: > We have a little problem in Eclipse CDT related to queries being sent on > the MI channel. GDB sends queries on the MI stream and waits for an > answer (y or n), but since CDT will never answer, it causes a deadlock. > > Note that this is only a problem when using MI as a side-channel > (new-ui) on a dedicated tty. It doesn't happen if GDB's input/output > streams are pipes, for example. In that case, the queries are > auto-answered as they should. I think we could have a testsuite test for this, as the 'new-ui'-related testcases create a pty for the secondary MI channel ("separate-mi-tty")? Thanks, Pedro Alves