Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb@sourceware.org>
Subject: Re: UST integration is broken
Date: Mon, 09 Jan 2012 15:58:00 -0000	[thread overview]
Message-ID: <4F0B0E80.8070307@codesourcery.com> (raw)
In-Reply-To: <m3sjjsgrv2.fsf@redhat.com>

On 01/07/2012 10:37 AM, Sergio Durigan Junior wrote:
> I am working on something related to static tracepoints markers, which
> is related to UST (http://lttng.org/ust).  I did some modifications on
> the code, and was trying to test the result, when I realized I did not
> have UST installed here.  Ok, so I decided to compile it and install
> locally just for a quick test, and after some time struggling with
> compilation flags, I noticed that the current UST does not support GDB
> anymore.  For more information, see this commit:
> 
> http://git.lttng.org/?p=ust.git;a=commit;h=fe566790e6be3f27f0befd85b715a3e84977bf6c
> 

libinproctrace.so is unable to build with UST after 0.11
release.  GDB support in UST was temporarily removed from UST by the
commit you pointed out.  GDB CVS trunk is still able to build with UST
0.11 and URCU 0.5.3.

> I also noticed that the header file ust/ust.h is not installed, thus
> making the configure process useless.  I am sending this message because
> I am in doubt about what to do: should we completely remove the support
> from GDB (since according to the commit message above, the
> implementation is going to be revamp'ed), or just temporarily disable
> it?  I was going to send a patch for the latter, but decided to ask
> first.

If UST 0.11 is installed, everything still works well, otherwise, UST
stuff will not be compiled.  So I disagree to disable it temporarily.

There has been a PR for this issue,

  gdb 7.2 can't build with lttng-ust 0.12
  http://sourceware.org/bugzilla/show_bug.cgi?id=12699

-- 
Yao (齐尧)


      parent reply	other threads:[~2012-01-09 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07  2:38 Sergio Durigan Junior
2012-01-07  3:20 ` Sergio Durigan Junior
2012-01-09 14:52 ` Tom Tromey
2012-01-09 15:58 ` 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=4F0B0E80.8070307@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb@sourceware.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