From mboxrd@z Thu Jan  1 00:00:00 1970
From: yangw.wang5@unb.ca (Yang Wang)
Date: Wed, 23 Jan 2013 20:09:30 +0000
Subject: [lttng-dev] bug?
Message-ID: <8E0A14A4C9B95B459AE214584119C1EB3BC909B3@Hal.ad.unb.ca>

Hello,

I am Yang Wang, I am currently using lttng to trace my JVM.

During my using lttng in tracing JVM, I found three problems,

 1) in lttng-ust-2.1.0/include/lttng/ust-tracepoint-event.h

     why using an assertion "assert(!ret);"  (Line676)?
     not allowing double registering and init?
     if double registering or initialization (provider), why not allowed just returning silently instead
      of aborting"? How about comments assert(!ret); ==>//assert(!ret); what is the side-effects
      of doing this?

 2) The other problem is in ./userspace-rcu-0.7.5/urcu/list.h Line85

  I have to add a guard "if" statement as the assertion in my program fails otherwise

  static inline void
  __cds_list_del (struct cds_list_head *prev, struct cds_list_head *next)
  {
   if (prev != NULL && next != NULL) {
      //assert(prev != NULL && next != NULL);
      next->prev = prev;
      prev->next = next;
  }

 3) Now my instrumented prog is ready to run. Here is my commands:
     lttng create
     lttng enable-event -u -a
     lttng start
     ./prog

    The (lttng) instrumented prog is stuck there without any outputs related to lttng tracing, how can I know what happen inside.
    In other words, does lttng have any mechanism to trace itself?

   Thanks

   Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20130123/334ff07a/attachment.html>