From: Yao Qi <yao@codesourcery.com>
To: Suchakra Sharma <suchakrapani.sharma@polymtl.ca>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, <gdb@sourceware.org>
Subject: Re: Debugging agent library
Date: Thu, 09 May 2013 01:01:00 -0000 [thread overview]
Message-ID: <518AF563.2070204@codesourcery.com> (raw)
In-Reply-To: <1368042096.5194.41.camel@station15.dorsal.polymtl.ca>
On 05/09/2013 03:41 AM, Suchakra Sharma wrote:
> Thanks for your detailed reply. We were able to rectify the issue. We
> tried with a clean install of gdb and libdagent on another machine which
> did not show any issue. The problem was probably because we tinkered
> around the dagent code a bit before using it. All works well now.
>
Good.
> Indeed, dynamic tracing with GDB is getting more awesome day by day
> (this view is reinforced by some tests I ran in-house which really show
> how powerful and fast it is) A you know LTTng/UST already has quite fast
> static tracing features, so our main aim is to get dynamic tracing
> infrastructure of GDB in LTTng/UST for fast dynamic user space tracing
> in an elegant way. We are not 100% clear how it shall be achieved at
> this moment but we are exploring all avenues for now. At first glance it
> looked as if we could do it using this library coupled with GDB
> (controlled through LTTng/UST acting as our tool). Your ideas are
> welcome and we surely shall contribute once we get a good knack of how
> to extend GDB's functionality for our use.
GDB/GDBserver is able to control UST static tracepoint through agent,
but UST is 0.11 and URCU is 0.5.3, which is a little bit old. In UST
0.12 release, the GDB support is removed unfortunately. Probably you
can have a look at testsuite/gdb.trace/strace.exp to see how
GDB/GDBserver interact with UST static tracepoints.
--
Yao (é½å°§)
prev parent reply other threads:[~2013-05-09 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 19:21 Suchakra Sharma
[not found] ` <5188AE42.50308@codesourcery.com>
2013-05-07 18:50 ` Simon Marchi
2013-05-08 2:16 ` Yao Qi
2013-05-08 19:42 ` Suchakra Sharma
2013-05-09 1:01 ` Yao Qi [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=518AF563.2070204@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=suchakrapani.sharma@polymtl.ca \
/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