Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: luccisa@cisco.com (Alex Luccisano (luccisa))
Subject: [ltt-dev] no metadata tracefile
Date: Thu, 22 Sep 2011 08:57:17 -0500	[thread overview]
Message-ID: <979ADE62523D094FB865A35E3DB0D83F0326DC0E@XMB-RCD-207.cisco.com> (raw)
In-Reply-To: <20110922133617.GA30684@Krystal>

Hi Mathieu,

> -----Original Message-----
> From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]
> Sent: Thursday, September 22, 2011 09:36
> To: Ji Zhai
> Cc: ltt-dev at lists.casi.polymtl.ca
> Subject: Re: [ltt-dev] no metadata tracefile
> 
> * Ji Zhai (Ji.Zhai at ca.flextronics.com) wrote:
> > Hi Mathieu,
> >
> > I'd like to know if you have had time to review my question. If
> > possible, can you please give me a guide/direction to debug this
> > issure?
> 
> Hi Ji,
> 
> Sorry, I am pretty busy on UST 2.0 these days.
> 
> About your question you might want to try adding "printf" statements
> within marker.c in UST, and also try compiling UST with -DUST_DEBUG=1
so
> enable debugging output. I fear there is a linker issue on your
system,
> but unfortunately I don't have access to your setup.
> 
> Try comparing the outputs of a simple test program in your powerpc
> target setup, in a native host x86 setup, and in a native host x86_64
> setup. This way you should be able to identify what is missing.

[AL:] I've been helping with this effort and what you describe above is
exactly what I did here:

http://lists.casi.polymtl.ca/pipermail/ltt-dev/2011-September/005135.htm
l

There seems to be some problem with __start__ust_marker_ptrs.  How
should this be linked with the "foo" binary?

Regards,
Alex

> 
> Best regards,
> 
> Mathieu



  reply	other threads:[~2011-09-22 13:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 20:47 Ji Zhai
2011-09-13 18:47 ` Ji Zhai
2011-09-13 18:47   ` Ji Zhai
2011-09-13 18:57   ` Mathieu Desnoyers
     [not found]   ` <BLU0-SMTP70493DBB789A80AE9E466A96050@phx.gbl>
2011-09-13 19:22     ` Ji Zhai
2011-09-13 20:03       ` Alexandre Montplaisir
2011-09-14 18:05         ` Ji Zhai
2011-09-14 18:05           ` Ji Zhai
2011-09-15 13:31           ` Alexandre Montplaisir
2011-09-15 15:03             ` Ji Zhai
2011-09-15 16:21               ` Alexandre Montplaisir
2011-09-15 16:21           ` Mathieu Desnoyers
     [not found]           ` <BLU0-SMTP10DC664C76B1F77D7B84BC96070@phx.gbl>
2011-09-15 19:27             ` Ji Zhai
2011-09-15 19:27               ` Ji Zhai
2011-09-18 22:23               ` Mathieu Desnoyers
     [not found]               ` <BLU0-SMTP44E853CF05E12EB77650D196080@phx.gbl>
2011-09-19 14:12                 ` Ji Zhai
2011-09-19 15:02                   ` Mathieu Desnoyers
     [not found]                   ` <BLU0-SMTP423756B62AF3BC179695E8960B0@phx.gbl>
2011-09-19 15:18                     ` Ji Zhai
2011-09-22 13:25                       ` Ji Zhai
2011-09-22 13:36                         ` Mathieu Desnoyers
2011-09-22 13:57                           ` Alex Luccisano (luccisa) [this message]
2011-09-22 15:12                             ` Mathieu Desnoyers
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31 19:23 Ji Zhai

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=979ADE62523D094FB865A35E3DB0D83F0326DC0E@XMB-RCD-207.cisco.com \
    --to=luccisa@cisco.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