From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21975 invoked by alias); 23 Oct 2009 04:46:06 -0000 Received: (qmail 21925 invoked by uid 22791); 23 Oct 2009 04:46:04 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.redpinesignals.com (HELO mail.redpinesignals.com) (203.196.161.92) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Oct 2009 04:45:59 +0000 Received: from [192.168.40.84] ([192.168.40.84]) (authenticated user sumanth.gundapneni@redpinesignals.com) by mail.redpinesignals.com; Fri, 23 Oct 2009 10:05:11 +0530 Message-ID: <4AE132F6.9010800@redpinesignals.com> Date: Fri, 23 Oct 2009 15:54:00 -0000 From: sumanth User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Michael Snyder CC: gdb Subject: Re: TRACE implementation References: <4ADD70C8.2040800@redpinesignals.com> <4ADDF8D4.4010100@vmware.com> <4ADE9702.20300@redpinesignals.com> <4ADF17B1.6030100@vmware.com> In-Reply-To: <4ADF17B1.6030100@vmware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00345.txt.bz2 Hi Michael, Very pleased with the information you provided. Still I have certain doubts in mind. Tracepoints can b implemented through either remote stubs or gdbserver or gdb agents (byte-coding). Is this true?.................................................. which can be best suited to me as I am accessing my fpga/processor through a parallel port jtag. I dont want to burden my processor by running a server on it. The problem here , I googled in net and I didn't even find a single prototype to have a fell of how to trace data(trace points) on my target . Thanks, Sumanth G Michael Snyder wrote: > sumanth wrote: >> Hi , >> >> I am talking about "gdb tracepoints" only. I am asking for >> "How can I implement them in GDB ?" > > Great. Thanks for the clarification. > Partial answer: you don't have to implement them in gdb. > They're already implemented in gdb. > >> means, where I can start with. Heard something about remote stubs > > Yes, that's correct. GDB already knows how to tell a stub > to collect trace data. You need to implement a stub that > understands the trace commands that gdb will send to it. > >> Michael , Can you be a bit more brief on "published API" which >> you mentioned in your last response. > > Sure. First, if you haven't seen this already, you probably > want to look at it: http://sourceware.org/gdb/talks/esc-west-1999 > There is a white paper, a slide presentation, and other documents. > It's all old, but not obsolete, since very little additional > development has been done since then. > > Second, the remote protocol messages that your stub will > need to implement are specified here: > > http://sourceware.org/gdb/current/onlinedocs/gdb_37.html#SEC683 > > I should let you know that some folks at Code Sourcery have > recently been doing some work with tracepoints. If you were > interested in hiring someone to do the work for you on contract, > either I or one of the other maintainers could probably put you > in contact with someone privately. > > Good luck, > Michael > > > >