From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Increase the bar of printing `handling possible serial event'
Date: Fri, 11 Nov 2011 06:10:00 -0000 [thread overview]
Message-ID: <4EBCBC34.7060400@codesourcery.com> (raw)
In-Reply-To: <201111101941.30469.pedro@codesourcery.com>
On 11/11/2011 03:41 AM, Pedro Alves wrote:
> I've found it more than once very useful when debugging non-stop/async mode
> issues, where the order of serial and target events isn't predictable,
> and knowing when a packet was just handled can help figure out
> following weird behaviors.
>
OK, I understand.
> If it bothers so much, I could go with outputting it only when non_stop is
No. "--debug=N" is a right way to go in long term.
--
Yao (é½å°§)
prev parent reply other threads:[~2011-11-11 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 6:28 Yao Qi
2011-11-10 19:41 ` Pedro Alves
2011-11-10 22:04 ` Stan Shebs
2011-11-11 6:10 ` 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=4EBCBC34.7060400@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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