public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Abhishek Karoliya <abhikaro@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Tracepoints and Timestamps
Date: Mon, 07 Nov 2011 14:53:00 -0000	[thread overview]
Message-ID: <CAEEVgBXEg9D4Z8U5Ln0d7Mg9F14dT18A5KHdnGd98xJsi63xtg@mail.gmail.com> (raw)
In-Reply-To: <CANFwon3=4jObaaphqveRjF8rrBH6aRAxW1p=r4wZx6xxQOFSFQ@mail.gmail.com>

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.

Cheers!
Abhi

On Mon, Nov 7, 2011 at 6:40 AM, Hui Zhu <teawater@gmail.com> wrote:
> If you use the gdbserver that include in GDB source, you can access
> special tvariable $trace_timestamp.
>
> If not, I think maybe you can add a special tvariable that access to
> timebase registers (tbl and tbu)  to gdbserver.  Then you can collect
> it when you want it.
>
> Thanks,
> Hui
>
>
> On Sat, Nov 5, 2011 at 03:05, Abhishek Karoliya <abhikaro@gmail.com> wrote:
>> Hi,
>>
>>   I am remote debuging a multi threaded app on a powerpc e500v2 dual
>> processor running linux 2.6.32 while the host gdb is x86_64 linux
>> machine. The version of gdb is 7.3.1. On hitting a tracepoint, I want
>> to collect the timestamp. I am wondering is there is any way of doing
>> it currently on this gdb. If not, I was wondering if I can collect the
>> timebase registers (tbl and tbu). The current register dump does not
>> show the contents of these register on e500v2 although I have seen an
>> entry for other powerpc processor.
>>
>> Is there a way I can quickly add support for these registers. If
>> someone can point me to file/doc/previous patches to do this I will be
>> grateful.
>>
>>  Cheers!
>> Abhi
>>
>

  reply	other threads:[~2011-11-07 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEEVgBVFNRLqG67VwzF1D63Ro57Sww1HOwyrPBywRPBnHt5Hjg@mail.gmail.com>
2011-11-04 19:06 ` Abhishek Karoliya
2011-11-07  6:41   ` Hui Zhu
2011-11-07 14:53     ` Abhishek Karoliya [this message]
2011-11-07 16:15       ` Stan Shebs
2011-11-07 17:20         ` Pedro Alves

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=CAEEVgBXEg9D4Z8U5Ln0d7Mg9F14dT18A5KHdnGd98xJsi63xtg@mail.gmail.com \
    --to=abhikaro@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=teawater@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).