[lttng-dev] about how to trouble-shooting when lttng-sessiond crash happens.

[lttng-dev] about how to trouble-shooting when lttng-sessiond crash happens.

[Jérémie Galarneau]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

Hi Jenny,

LTTng 2.5 has been unsupported for a while now. The oldest supported
version is LTTng 2.7. You may want to update to the latest LTTng 2.8.x
release and see if the problem persists.

As for how to collect a back trace, if you have collected a core file,
open it in GDB and use:

(gdb) thread apply all bt full

This should provide you with a complete back trace of all threads at
the time of the crash.

Regards,
Jérémie

On Tue, Jul 26, 2016 at 5:03 AM, Jenny Gu <jenny.gu at ericsson.com> wrote:
> Hi all,
>
>
>
> We’re now applying lttng 2.5 in our system but we experienced lttng-sessiond
> crash. Could you show how to dump the back trace of the core? Thanks very
> much.
>
>
>
> BRs,
>
> Jenny.
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com