Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: gdbserver tracepoints support proper
Date: Tue, 06 Apr 2010 20:13:00 -0000	[thread overview]
Message-ID: <4BBB95B7.4070106@codesourcery.com> (raw)
In-Reply-To: <w2le394668d1004061254zef8e2cb5tc4a69996d5c51e4b@mail.gmail.com>

Doug Evans wrote:
> On Sun, Apr 4, 2010 at 4:21 PM, Pedro Alves <pedro@codesourcery.com> wrote:
>   
>> This finally adds a trace agent to gdbserver, and enough glue
>> to make it work for x86-linux.
>>     
>
> For reference sake,
> there's no technical reason why gdb itself can't support tracepoints, right?
> [IWBN to use tracepoints on linux, for example, without having to use gdbserver]
>
>   

I suppose not - you could try defining native versions of the tracepoint 
methods, convert tracepoint insertion to breakpoint insertion, manage 
the trace buffer within GDB, have agent expression evaluation call 
target vector to get registers or memory.  You'd have to do some 
trickiness with bpstats, and maybe extend target vector, so that if GDB 
sees a tracepoint hit via remote protocol, it's a bad error, but if 
native, it's handled more like a breakpoint with a command list.

Stan


  reply	other threads:[~2010-04-06 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 23:22 Pedro Alves
2010-04-06 19:55 ` Doug Evans
2010-04-06 20:13   ` Stan Shebs [this message]
2010-04-09  3:43 ` 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=4BBB95B7.4070106@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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