From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Tom Tromey <tromey@redhat.com>
Cc: "Cui, Dexuan" <dexuan.cui@intel.com>,
"'ltt-dev@lists.casi.polymtl.ca'"
<ltt-dev@lists.casi.polymtl.ca>,
"'gdb@sourceware.org'" <gdb@sourceware.org>,
systemtap@sources.redhat.com, Josh Stone <jistone@redhat.com>
Subject: Re: [ltt-dev] gdb-7.2 can't build with lttng-ust-0.12
Date: Tue, 26 Apr 2011 21:42:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP16A0C8CD677BBD4910355496990@phx.gbl> (raw)
In-Reply-To: <m34o5ksvcv.fsf@fleche.redhat.com>
* Tom Tromey (tromey@redhat.com) wrote:
> >>>>> "Dexuan" == Cui, Dexuan <dexuan.cui@intel.com> writes:
>
> Mathieu> Also, we should reopen the discussion on the way the UST Markers
> Mathieu> collect the registers for GDB, because the current way involves a
> Mathieu> _lot_ of ugly assembly code. It should be possible to only use a
> Mathieu> volatile inline asm to specify input constraints on the target marker
> Mathieu> parameters, and keep the instruction pointer address that corresponds
> Mathieu> to this inline asm in a section known by gdb (so gdb could use the
> Mathieu> drawf info to fetch data from registers/memory). If you can ensure
> Mathieu> that this would fit gdb's requirements, I could clean up the marker
> Mathieu> code and we could resync the APIs together. We could also provide
> Mathieu> this for UST Tracepoints in the same go, with pretty much the same
> Mathieu> interface as we'd use for UST Markers. I am aware that this would
> Mathieu> require change on the GDB side, but I think it's better to
> Mathieu> synchronise our effort rather than to shoot at different targets.
>
> I am not totally clear on the proposal here.
>
> If this means reusing the <sys/sdt.h> stuff, then there are gdb patches
> already submitted to fully support that; and updating the existing code
> to also use it should not be very difficult. See gdb-patches from the
> last month or two.
Yes, the goal is to rely on sdt.h as soon as it supports a e.g.
STAP_PROBEV (with variable number of args). The Josh Stone found a neat
trick to do it, and I think he is preparing an updated version.
The only concern here is the packaging: if we depend on sdt.h, we have
to either ship it with UST, or have one more dependency on a package
available for all architectures that only contain this header. Thoughts ?
It's good to hear that GDB is already planning on supporting that.
Thanks,
Mathieu
>
> If instead you mean something else, it would be useful to have more
> information. From your description it sounds like this may be a
> different design from SDT v3; but note that SDT v2 tried to use DWARF to
> access the parameters and ran into various problems. I can get details
> on the failure modes if this is what you intend.
>
> Dexuan> Unluckily I'm pretty new to gdb and know few about this now.
> Dexuan> Let me Cc the gdb mailing list for more thoughts(hope this cross-posting
> Dexuan> wouldn't bother people).
>
> Cross-posting in cases like this is fine, even preferable.
>
> I don't know anything about the gdbserver bits here. It seems to me
> that it would be reasonable to have gdbserver compile against various
> versions of UST.
>
> Tom
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-04-26 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1865303E0DED764181A9D882DEF65FB6931C75A5AA@shsmsx502.ccr.corp.intel.com>
[not found] ` <BLU0-SMTP7051C411EF9E3864329F4596960@phx.gbl>
2011-04-26 1:51 ` Cui, Dexuan
2011-04-26 18:47 ` Tom Tromey
2011-04-26 21:42 ` Mathieu Desnoyers [this message]
[not found] ` <BLU0-SMTP3759F7830D97C89E9BCE9796990@phx.gbl>
2011-04-27 0:26 ` Josh Stone
[not found] ` <BLU0-SMTP45CC9DEEE33FD5A526EB3896990@phx.gbl>
2011-04-27 14:32 ` Tom Tromey
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=BLU0-SMTP16A0C8CD677BBD4910355496990@phx.gbl \
--to=compudj@krystal.dyndns.org \
--cc=dexuan.cui@intel.com \
--cc=gdb@sourceware.org \
--cc=jistone@redhat.com \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=systemtap@sources.redhat.com \
--cc=tromey@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