Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] gdb-7.2 can't build with lttng-ust-0.12
Date: Mon, 25 Apr 2011 10:42:53 -0400	[thread overview]
Message-ID: <BLU0-SMTP231B91CFDC5319D87FFE1D96960@phx.gbl> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6931C75A5AA@shsmsx502.ccr.corp.intel.com>

* Cui, Dexuan (dexuan.cui at intel.com) wrote:
> Due to the API changes in lttng-ust 0.12,  gdb's latest version 7.2 can't build with lttng-ust:
> http://sourceware.org/ml/gdb/2011-04/msg00140.html
> 
> Hope somebody here can help gdb to work with ust 0.12. :-)

Hi Dexuan,

We're currently doing instrumentation API changes in UST. At the moment,
it is in the git tree, planned for release in UST 0.13. Our goal is to
perform this painful (but required) step sooner than later so that we
minimize the amount of pain for our user-base.

Also, we should reopen the discussion on the way the UST Markers collect
the registers for GDB, because the current way involves a _lot_ of ugly
assembly code. It should be possible to only use a volatile inline asm
to specify input constraints on the target marker parameters, and keep
the instruction pointer address that corresponds to this inline asm in a
section known by gdb (so gdb could use the drawf info to fetch data from
registers/memory). If you can ensure that this would fit gdb's
requirements, I could clean up the marker code and we could resync the
APIs together. We could also provide this for UST Tracepoints in the
same go, with pretty much the same interface as we'd use for UST
Markers. I am aware that this would require change on the GDB side, but
I think it's better to synchronise our effort rather than to shoot at
different targets.

Thanks,

Mathieu

> 
> Thanks!
> 
> -- Dexuan
>  
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2011-04-25 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 12:51 Cui, Dexuan
2011-04-25 14:42 ` Mathieu Desnoyers [this message]
     [not found] ` <BLU0-SMTP7051C411EF9E3864329F4596960@phx.gbl>
2011-04-26  1:49   ` Cui, Dexuan
2011-04-26 18:47     ` Tom Tromey
2011-04-26 21:41       ` Mathieu Desnoyers
     [not found]       ` <BLU0-SMTP3759F7830D97C89E9BCE9796990@phx.gbl>
2011-04-27  0:26         ` Josh Stone
     [not found]       ` <BLU0-SMTP45CC9DEEE33FD5A526EB3896990@phx.gbl>
2011-04-27 14:31         ` 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-SMTP231B91CFDC5319D87FFE1D96960@phx.gbl \
    --to=compudj@krystal.dyndns.org \
    /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