From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113627 invoked by alias); 10 Oct 2018 09:39:45 -0000 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 Received: (qmail 113586 invoked by uid 89); 10 Oct 2018 09:39:44 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:user, channel X-HELO: relay.fit.cvut.cz Received: from relay.fit.cvut.cz (HELO relay.fit.cvut.cz) (147.32.232.237) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 10 Oct 2018 09:39:41 +0000 Received: from imap.fit.cvut.cz (imap.fit.cvut.cz [147.32.232.238]) by relay.fit.cvut.cz (8.15.2/8.15.2) with ESMTPS id w9A9da91073077 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 10 Oct 2018 11:39:38 +0200 (CEST) (envelope-from jan.vrany@fit.cvut.cz) Received: from sao (ip-94-112-144-59.net.upcbroadband.cz [94.112.144.59]) (authenticated bits=0 as user vranyj1) by imap.fit.cvut.cz (8.15.2/8.15.2) with ESMTPSA id w9A9dZLL004531 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 10 Oct 2018 11:39:36 +0200 (CEST) (envelope-from jan.vrany@fit.cvut.cz) Message-ID: Subject: =tsv-created MI event outputs extra "\n" on MI channel From: Jan Vrany To: "gdb@sourceware.org" Date: Wed, 10 Oct 2018 09:39:00 -0000 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00022.txt.bz2 Hi, I just discovered that =tsv-created event contains an extra \n at the end (i mean, backslash + n): gdbserver localhost:1234 ./factorial1 then gdb -i mi2 -ex "target extended-remote localhost:1234" produces: ~"Remote debugging using localhost:1234\n" =tsv-created,name="trace_timestamp",initial="0"\n (gdb) Note the literal \n at the end of =tsv-created. This is IMO not a valid MI record, according to documentation. Looking at the code, this has been introduced in commit 73ab01a07df, from Jun 2016, so this is an old change. Is this something that is worth fixing or is it something all other MI consumers (but mine :-) are already used to so it cannot be changed? Best, Jan