From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH V2] Don't print too much if remote_debug is on
Date: Fri, 13 Jan 2017 15:46:00 -0000 [thread overview]
Message-ID: <20170113154614.GE28060@E107787-LIN> (raw)
In-Reply-To: <1481034118-17745-1-git-send-email-yao.qi@linaro.org>
On 16-12-06 14:21:58, Yao Qi wrote:
> gdb:
>
> 2016-12-06 Yao Qi <yao.qi@linaro.org>
>
> * remote.c (REMOTE_DEBUG_MAX_CHAR): New macro.
> (putpkt_binary): Print only REMOTE_DEBUG_MAX_CHAR chars in debug
> output.
> (getpkt_or_notif_sane_1): Likewise.
I pushed it in.
--
Yao (é½å°§)
prev parent reply other threads:[~2017-01-13 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 15:38 [PATCH] " Yao Qi
2016-11-29 15:46 ` Luis Machado
2016-11-30 12:54 ` Yao Qi
2016-11-30 14:01 ` Luis Machado
2016-12-01 20:05 ` Gary Benson
2016-11-30 19:28 ` Pedro Alves
2016-12-06 14:22 ` [PATCH V2] " Yao Qi
2017-01-13 15:46 ` Yao Qi [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=20170113154614.GE28060@E107787-LIN \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
/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