From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>,
Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Make gdb.mi/mi-sym-info.exp more robust against timeouts
Date: Fri, 30 Apr 2021 09:41:39 -0400 [thread overview]
Message-ID: <074d5247-caa5-f0ec-d938-59e71e9f566b@polymtl.ca> (raw)
In-Reply-To: <2a638604-5146-6c0d-07fd-a0073ce61d31@linaro.org>
On 2021-04-30 9:34 a.m., Luis Machado wrote:
> What I'm unsure about is if the MI protocol cares about line breaks or not. If not, there is no reason we should be putting out such long line, as it is hard on the test infrastructure.
From what I remember, I don't think there can be newlines in the output.
Each output record is on its own line.
Simon
prev parent reply other threads:[~2021-04-30 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 9:27 Tom de Vries
2021-04-30 12:55 ` Luis Machado via Gdb-patches
2021-04-30 13:05 ` tdevries
2021-04-30 13:06 ` Simon Marchi via Gdb-patches
2021-04-30 13:20 ` Luis Machado via Gdb-patches
2021-04-30 13:28 ` Simon Marchi via Gdb-patches
2021-04-30 13:34 ` Luis Machado via Gdb-patches
2021-04-30 13:41 ` Simon Marchi via Gdb-patches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=074d5247-caa5-f0ec-d938-59e71e9f566b@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox