From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23636 invoked by alias); 10 Nov 2011 22:04:44 -0000 Received: (qmail 23625 invoked by uid 22791); 10 Nov 2011 22:04:42 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-masked.atl.sa.earthlink.net (HELO elasmtp-masked.atl.sa.earthlink.net) (209.86.89.68) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Nov 2011 22:04:29 +0000 Received: from [70.170.59.51] (helo=macbook2.local) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1ROcjU-0007mZ-T9 for gdb-patches@sourceware.org; Thu, 10 Nov 2011 17:04:28 -0500 Message-ID: <4EBC4A67.9010106@earthlink.net> Date: Thu, 10 Nov 2011 22:04:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: gdb-patches@sourceware.org Subject: Re: [patch] Increase the bar of printing `handling possible serial event' References: <4EBB6ED6.7050408@codesourcery.com> <201111101941.30469.pedro@codesourcery.com> In-Reply-To: <201111101941.30469.pedro@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da940f3c0c89e5bb9065e3d8d69d2c1bae605350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00300.txt.bz2 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