Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: ankit thukral <ankit_plug@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: about QTro packet (tracepoints)
Date: Wed, 01 Oct 2003 06:43:00 -0000	[thread overview]
Message-ID: <vt21xtxmphr.fsf@zenia.home> (raw)
In-Reply-To: <20031001062341.86372.qmail@web60106.mail.yahoo.com>

ankit thukral <ankit_plug@yahoo.com> writes:

>  hi all,
>         i was reading the packets' format in GDB for
>  tracepoints (like QTStart,QTinit etc.) and came
>  across
>  "QTro" packet format.i learned that this packet
>  transmits the addresses of all the LOADABLE
>  READ-ONLY
>  sections to the remote stub so that the latter can
>  always entertain a request for data belonging to
>  these
>  address ranges,even if this was not specified as a
>  tracepoint action by the user.
>        would it not be a better option to let the
>  remote stub collect this information of it's own
>  (from
>  it's own copy of the executable) rather than GDB
>  transmitting it across the network which definitely
>  is
>  more costly in terms of time delay suffered by the
>  process which becomes all the more costly while
>  debugging a real-time application?

If you're running Linux or something like that on the target, sure.
But tracepoints also need to work on systems with no operating system
at all, just a stub.  In that case, the stub has no idea which
sections are read-only and which sections may change.

The QTro packet is only sent once, when the trace experiment begins;
is it actually a major time sink?  How many sections do you have?


      reply	other threads:[~2003-10-01  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  6:23 ankit thukral
2003-10-01  6:43 ` Jim Blandy [this message]

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=vt21xtxmphr.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=ankit_plug@yahoo.com \
    --cc=gdb@sources.redhat.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