From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23006 invoked by alias); 7 Nov 2011 16:15:42 -0000 Received: (qmail 22981 invoked by uid 22791); 7 Nov 2011 16:15:39 -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-curtail.atl.sa.earthlink.net (HELO elasmtp-curtail.atl.sa.earthlink.net) (209.86.89.64) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 07 Nov 2011 16:15:24 +0000 Received: from [70.170.59.51] (helo=macbook2.local) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1RNRr2-00075V-66 for gdb@sourceware.org; Mon, 07 Nov 2011 11:15:24 -0500 Message-ID: <4EB80415.7010304@earthlink.net> Date: Mon, 07 Nov 2011 16:15: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@sourceware.org Subject: Re: Tracepoints and Timestamps References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da940b341bf3903c97335f6690306476d634e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00049.txt.bz2 On 11/7/11 6:53 AM, Abhishek Karoliya wrote: > Hi Hui, > > Thanks for the pointer ... However after going through the > gdbserver source code, I realise that there is no tracepoint support > for linux-ppc. So now I have a even bigger problem on my hand. > > Does anyone know if I can ppc tracepoint support being actively > developed and if I can lay my hands on this experimental code. > The tracepoint support in GDBserver is pretty generic, and if you don't need fast tracepoints, there's not really anything that is arch-specific. I would suggest enabling target_supports_tracepoints for ppc and letting us know how it goes. If it "just works", then we could change the target_supports_tracepoints test to make it unconditional - fast tracepoint support has its own availability check at runtime, it could subsume the architecture check. Stan stan@codesourcery.com