From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Increase the bar of printing `handling possible serial event'
Date: Thu, 10 Nov 2011 22:04:00 -0000 [thread overview]
Message-ID: <4EBC4A67.9010106@earthlink.net> (raw)
In-Reply-To: <201111101941.30469.pedro@codesourcery.com>
On 11/10/11 11:41 AM, Pedro Alves wrote:
> On Thursday 10 November 2011 06:27:34, Yao Qi wrote:
>> Hi,
>> When I debug gdbserver by setting debug_thread to 1, I get many lines
>> of `handling possible serial event' in log, which dose not carry any
>> useful information for debugging purpose.
>>
>> This patch is to increase the threshold of printing this sentence. Or we
>> may remove this print completely, because I can't figure out a case
>> some one wants to read many lines of `handling possible serial event'
>> in log.
> 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.
>
> If it bothers so much, I could go with outputting it only when non_stop is
> on. Just bumping is not good, because you can't set debug_thread to anything
> other than 1 or 0 without recompiling gdbserver, and that's not good when
> asking users for logs.
>
--debug=2 ?
Might as well invest, the poor code is getting plenty of use/abuse. :-)
Stan
next prev parent reply other threads:[~2011-11-10 22:04 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 [this message]
2011-11-11 6:10 ` Yao Qi
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=4EBC4A67.9010106@earthlink.net \
--to=stanshebs@earthlink.net \
--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