Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] lttng-relayd core
Date: Tue, 28 Apr 2015 15:21:44 +0000 (UTC)	[thread overview]
Message-ID: <1598887302.39240.1430234504111.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAM5kDqxgbBpA29j3J66BkMoFJidEhPiHeJ+Vdtp8-3PacrD5ww@mail.gmail.com>

Hi Anand, 

This bug report lacks a lot of information we need to reproduce the 
issue. We'll soon come up with a "bug report guideline" on the lttng.org 
website. 

Also, we can't help but noticing that the amount of support you have been 
requiring those past months seems better suited to the commercial LTTng 
support offered by EfficiOS. In addition to give you the amount of support 
you need, this is one of the main mechanisms for funding LTTng project 
maintenance work. 

Best Regards, 

Mathieu 

----- Original Message -----

> Hi All,

> Found this crash in 2.6.0
> Is there any open issue or workaround. Please help me with more info on this
> crash.

> (gdb) bt
> #0 0x00007fc62fe5bff9 in __GI_raise (sig=sig at entry=6)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1 0x00007fc62fe5f068 in __GI_abort () at abort.c:89
> #2 0x00007fc62fe55146 in __assert_fail_base (
> fmt=0x7fc62ff8d230 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
> assertion=assertion at entry=0x425ba2 "!obj->refcount",
> file=file at entry=0x425b92 "ctf-trace.c", line=line at entry=55,
> function=function at entry=0x425d80 <__PRETTY_FUNCTION__.5729>
> "ctf_trace_destroy") at assert.c:92
> #3 0x00007fc62fe551f2 in __GI___assert_fail (
> assertion=assertion at entry=0x425ba2 "!obj->refcount",
> file=file at entry=0x425b92 "ctf-trace.c", line=line at entry=55,
> function=function at entry=0x425d80 <__PRETTY_FUNCTION__.5729>
> "ctf_trace_destroy") at assert.c:101
> #4 0x00000000004110e0 in ctf_trace_destroy (obj=0x7fc61001e320)
> at ctf-trace.c:55
> #5 0x00000000004131f7 in session_destroy (
> session=session at entry=0x7fc61001a3c0) at session.c:177
> #6 0x0000000000413311 in session_try_destroy (ht=ht at entry=0x6330e0,
> session=session at entry=0x7fc61001a3c0) at session.c:149
> #7 0x00000000004078a7 in destroy_session (session=0x7fc61001a3c0,
> sessions_ht=0x6330e0) at main.c:1058
> #8 0x0000000000407a7d in destroy_connection (
> ---Type <return> to continue, or q <return> to quit---
> relay_connections_ht=<optimized out>, conn=0x7fc624000d00) at main.c:2418
> #9 0x000000000040aa11 in relay_thread_worker (data=<optimized out>)
> at main.c:2568
> #10 0x00007fc6301d8fe3 in start_thread (arg=0x7fc62e2f1700)
> at pthread_create.c:312
> #11 0x00007fc62ff0eafd in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
> (gdb)
> (gdb)

> Thanks,
> Anand Neeli

> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers 
EfficiOS Inc. 
http://www.efficios.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150428/d0f4ef08/attachment.html>


      reply	other threads:[~2015-04-28 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 14:52 Anand Neeli
2015-04-28 15:21 ` Mathieu Desnoyers [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=1598887302.39240.1430234504111.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.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