From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32146 invoked by alias); 8 Oct 2010 17:49:44 -0000 Received: (qmail 32126 invoked by uid 22791); 8 Oct 2010 17:49:43 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 08 Oct 2010 17:49:38 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 9A1533032; Fri, 8 Oct 2010 10:49:34 -0700 (PDT) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 90243C9AAC; Fri, 8 Oct 2010 10:49:34 -0700 (PDT) Message-ID: <4CAF59AE.9040004@vmware.com> Date: Fri, 08 Oct 2010 17:49:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20100903) MIME-Version: 1.0 To: Daniel Jacobowitz CC: "gdb-patches@sourceware.org" Subject: Re: [RFA] Quiet a tracepoint notification with gdbserver References: <20101008174145.GP23776@caradoc.them.org> In-Reply-To: <20101008174145.GP23776@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-10/txt/msg00146.txt.bz2 Daniel Jacobowitz wrote: > Since gdbserver now defines trace_timestamp, we get a notice after > connection. This is confusing if you're not trying to use > tracepoints. I suggest the attached patch; OK? > Thank you! I've found those messages bothersome, not because they confuse me but because they will confuse my users.