From: ankit thukral <ankit_plug@yahoo.com>
To: gdb@sources.redhat.com
Subject: about QTro packet (tracepoints)
Date: Wed, 01 Oct 2003 06:23:00 -0000 [thread overview]
Message-ID: <20031001062341.86372.qmail@web60106.mail.yahoo.com> (raw)
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?
hoping for a discussion on this,
ankit.
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
next reply other threads:[~2003-10-01 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 6:23 ankit thukral [this message]
2003-10-01 6:43 ` Jim Blandy
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=20031001062341.86372.qmail@web60106.mail.yahoo.com \
--to=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