From: Saul Wold <sgw@linux.intel.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: "'poky@yoctoproject.org'" <poky@yoctoproject.org>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Re: gdb and lttng-ust 0.12
Date: Sun, 24 Apr 2011 22:24:27 -0700 [thread overview]
Message-ID: <4DB5058B.3090904@linux.intel.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB69317AB0EDB@shsmsx502.ccr.corp.intel.com>
On 04/24/2011 10:14 PM, Cui, Dexuan wrote:
> Hi Saul,
> I prefer "continue with UST disabled in gdb" for now.
>
Ok, I have a patch queue'ed up already with this fix, I will push it as
part of a consolidated request later tonight.
> I'm investigating more to get an in-depth understanding about the issue. e.g., ust-0.11 doesn't break building gdb while ust-0.12 does -- however both 0.11 and 0.12 install /usr/include/ust/.
>
I agree, I am not sure why this is happening also, I thought that I did
installs of 0.11 and did not see the ust directory, maybe I did not
force or something. Maybe diff the marker.h files and see if there are
differences?
Sau!
> Thanks,
> -- Dexuan
>
> -----Original Message-----
> From: Cui, Dexuan
> Sent: 2011年4月25日 9:57
> To: 'Saul Wold'; 'Patches and discussions about the oe-core layer'
> Cc: poky@yoctoproject.org
> Subject: RE: gdb and lttng-ust 0.12
>
> Hi Saul,
> Thanks very much for the investigation!
> I can reproduce the issue now when I build gdb after building lttng-ust (previously looks I built them in the reverse order, so didn't catch it.)
>
> I haven't understood why this issue occurred after I upgraded ust from 0.11 to 0.12 as 0.11 actually installs /usr/include/ust, too. And gdb was not upgraded recently.
>
> I'm looking into this now and will update asap.
>
> Thanks,
> -- Dexuan
>
> -----Original Message-----
> From: Saul Wold [mailto:sgw@linux.intel.com]
> Sent: 2011年4月25日 4:17
> To: Cui, Dexuan; 'Patches and discussions about the oe-core layer'
> Cc: poky@yoctoproject.org
> Subject: gdb and lttng-ust 0.12
>
>
> Dexuan,
>
> It seems that when you updated lttng-ust to 0.12, it installed an
> /usr/include/ust directory that GDB now finds. This caused the
> gdbserver code to not build.
>
> I investigated this and it seems to be due to gdb having a dependency on
> UST that causes GDB not to compile. I think at this point we may want
> to continue with UST disabled in gdb.
>
> To reproduce this, ensure that lttng-ust-0.12 is built before building
> gdb and you should see a compilation failure.
>
> My concern here is that if fix the GDB compilation failures, what else
> is going to fail as far as debugging with UST enabled on the remote, I
> know this feature is something we want, and should probably report to
> the GDB upstream.
>
> The fix seems to be as simple as adding "--without-ust" to the gdb
> EXTRA_OECONF line.
>
> Comments?
>
next prev parent reply other threads:[~2011-04-25 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 20:16 gdb and lttng-ust 0.12 Saul Wold
2011-04-25 1:56 ` Cui, Dexuan
2011-04-25 5:14 ` Cui, Dexuan
2011-04-25 5:24 ` Saul Wold [this message]
2011-04-25 9:06 ` Cui, Dexuan
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=4DB5058B.3090904@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dexuan.cui@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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