org.lttng.lists.lttng-dev archive

409 archived articles, newest first (page 1 of 5). Latest articles →

[RELEASE] LTTng-modules 2.15.3 and 2.14.7 (Linux kernel tracer)
Mon, 17 Aug 2026 10:50:52 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13163
Re: babeltrace 2.1.2: sink.ctf.fs does not deduplicate identical clocks
Thu, 6 Aug 2026 14:45:53 -0400
Philippe Proulx via lttng-dev <[email protected]> • #13162
Re: babeltrace master: trace-compass is unable to open trace with index
Wed, 5 Aug 2026 14:10:05 +0000
Arnaud Fiorini via lttng-dev <[email protected]> • #13161
babeltrace master: trace-compass is unable to open trace with index
Wed, 5 Aug 2026 10:16:33 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13160
babeltrace 2.1.2: sink.ctf.fs does not deduplicate identical clocks
Tue, 4 Aug 2026 15:27:43 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13159
[RELEASE] LTTng 2.16.0-rc2 - Question de Perspective - Linux kernel and userspace tracer
Thu, 30 Jul 2026 15:58:58 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13158
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Sat, 11 Jul 2026 09:52:20 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13157
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Fri, 10 Jul 2026 11:57:53 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13156
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Fri, 10 Jul 2026 00:17:39 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13155
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 21:07:57 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13154
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 22:56:51 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13153
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 19:53:07 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13152
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 19:31:18 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13151
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 16:13:21 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13150
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 18:01:54 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13149
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 14:45:18 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13148
Re: CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 16:00:17 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13147
CPU affinity behavior of liburcu call-rcu per-cpu worker threads
Thu, 9 Jul 2026 14:48:07 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13146
[RELEASE] LTTng 2.16.0-rc1 - Question de Perspective - Linux kernel and userspace tracer
Wed, 24 Jun 2026 16:59:57 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13145
[RELEASE] LTTng-modules 2.14.6 and 2.15.2 (Linux kernel tracer)
Fri, 19 Jun 2026 14:56:17 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13144
[RELEASE] LTTng-tools 2.14.2 - Orbitales
Fri, 5 Jun 2026 15:33:54 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13143
[RELEASE] LTTng-tools 2.1 5.1 - Péché Mortel
Fri, 5 Jun 2026 15:32:08 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13142
[RELEASE] LTTng-UST 2.14.2 and 2.15.1 (Linux user-space tracer)
Fri, 22 May 2026 15:08:55 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13141
Re: How to show method entry/exit in Trace Compass?
Fri, 1 May 2026 19:31:43 +0000
Matthew Khouzam via lttng-dev <[email protected]> • #13140
How to show method entry/exit in Trace Compass?
Thu, 30 Apr 2026 18:01:32 +0100
David Aldrich via lttng-dev <[email protected]> • #13139
Re: Question about LTTng Kernel Probe Tracking
Tue, 7 Apr 2026 11:14:25 -0400
Amir Najafi Zadeh via lttng-dev <[email protected]> • #13138
[RELEASE] LTTng-modules 2.15.1 and 2.14.5 (Linux kernel tracer)
Fri, 24 Apr 2026 15:52:17 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13137
Re: Question about LTTng Kernel Probe Tracking
Wed, 8 Apr 2026 14:28:44 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13136
Re: Question about LTTng Kernel Probe Tracking
Tue, 7 Apr 2026 10:57:35 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13135
Question about LTTng Kernel Probe Tracking
Sat, 4 Apr 2026 21:02:11 -0400
Amir Najafi Zadeh via lttng-dev <[email protected]> • #13134
Re: [tracecompass-dev] Invitation: Trace Compass Monthly Project Meetings
Sat, 4 Apr 2026 20:45:27 -0400
Jonah Graham via lttng-dev <[email protected]> • #13133
[Userspace RCU] Introducing a new data structure: Fractal Trie
Wed, 1 Apr 2026 13:35:09 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13132
Re: Build-time tests fail if machine has a single CPU
Mon, 16 Mar 2026 09:57:55 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13131
Re: Build-time tests fail if machine has a single CPU
Mon, 9 Mar 2026 15:02:18 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13130
Re: Build-time tests fail if machine has a single CPU
Mon, 9 Mar 2026 18:12:14 +0100
Santiago Vila via lttng-dev <[email protected]> • #13129
Build-time tests fail if machine has a single CPU
Mon, 9 Mar 2026 18:10:08 +0100
Santiago Vila via lttng-dev <[email protected]> • #13128
[RELEASE] LTTng 2.15.0 - Péché Mortel - Linux kernel and userspace tracer
Fri, 13 Feb 2026 15:11:16 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13127
[RELEASE] LTTng-UST 2.13.10 (EOL) and 2.14.1 (Linux user-space tracer)
Fri, 13 Feb 2026 13:52:00 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13126
[RELEASE] LTTng-modules 2.13.23 (Linux kernel tracer)
Fri, 13 Feb 2026 13:48:46 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13125
[RELEASE] LTTng-modules 2.14.4 (Linux kernel tracer)
Mon, 9 Feb 2026 11:37:20 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13124
[RELEASE] LTTng-tools 2.14.1 - Orbitales
Thu, 29 Jan 2026 14:15:14 -0500
Jérémie Galarneau via lttng-dev <[email protected]> • #13123
Invitation: Trace Compass Monthly Project Meetings
Mon, 26 Jan 2026 16:42:16 +0000
Matthew Khouzam via lttng-dev <[email protected]> • #13122
[RELEASE] Userspace RCU 0.14.2 and 0.15.6
Mon, 26 Jan 2026 09:36:55 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13121
Re: How to build lttng on RHEL 9?
Wed, 21 Jan 2026 10:21:39 -0500
Michael Jeanson via lttng-dev <[email protected]> • #13120
Re: How to build lttng on RHEL 9?
Tue, 20 Jan 2026 16:12:15 +0000
David Aldrich via lttng-dev <[email protected]> • #13119
Re: How to build lttng on RHEL 9?
Mon, 19 Jan 2026 17:14:02 +0000
David Aldrich via lttng-dev <[email protected]> • #13118
Re: How to build lttng on RHEL 9?
Mon, 19 Jan 2026 12:02:44 -0500
Kienan Stewart via lttng-dev <[email protected]> • #13117
How to build lttng on RHEL 9?
Mon, 19 Jan 2026 16:00:44 +0000
David Aldrich via lttng-dev <[email protected]> • #13116
[RELEASE] LTTng 2.15.0-rc1 - Péché Morte l - Linux kernel and userspace tracer
Fri, 19 Dec 2025 17:31:58 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13115
Re: Question about LTTng Context
Thu, 11 Dec 2025 11:21:35 -0500
Amir Najafi Zadeh via lttng-dev <[email protected]> • #13114
Re: Question about LTTng Context
Thu, 11 Dec 2025 11:14:26 -0500
Michael Jeanson via lttng-dev <[email protected]> • #13113
Re: Question about LTTng Context
Thu, 11 Dec 2025 10:51:50 -0500
Amir Najafi Zadeh via lttng-dev <[email protected]> • #13112
Re: Question about LTTng Context
Thu, 11 Dec 2025 09:57:43 -0500
Michael Jeanson via lttng-dev <[email protected]> • #13111
Re: Question about LTTng Context
Thu, 11 Dec 2025 09:30:23 -0500
Kienan Stewart via lttng-dev <[email protected]> • #13110
Question about LTTng Context
Wed, 10 Dec 2025 21:40:45 -0500
Amir Najafi Zadeh via lttng-dev <[email protected]> • #13109
Re: babeltrace | sink.ctf.fs escaping of struct member names
Thu, 4 Dec 2025 16:07:43 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13108
Re: babeltrace | sink.ctf.fs escaping of struct member names
Thu, 4 Dec 2025 11:01:05 -0500
Philippe Proulx via lttng-dev <[email protected]> • #13107
Re: babeltrace | sink.ctf.fs escaping of struct member names
Thu, 4 Dec 2025 15:47:23 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13106
Re: babeltrace | sink.ctf.fs escaping of struct member names
Thu, 4 Dec 2025 10:15:27 -0500
Philippe Proulx via lttng-dev <[email protected]> • #13105
babeltrace | sink.ctf.fs escaping of struct member names
Thu, 4 Dec 2025 10:10:24 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13104
Re: babeltrace | sink.ctf.fs: add support to create LTTng index
Wed, 3 Dec 2025 09:58:22 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13103
Re: babeltrace | sink.ctf.fs: add support to create LTTng index
Mon, 1 Dec 2025 09:38:12 -0500
Philippe Proulx via lttng-dev <[email protected]> • #13102
babeltrace | sink.ctf.fs: add support to create LTTng index
Mon, 1 Dec 2025 09:34:23 +0000
"MOESSBAUER, Felix via lttng-dev" <[email protected]> • #13101
[RELEASE] Userspace RCU 0.15.5
Mon, 10 Nov 2025 20:35:35 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13100
[RELEASE] Userspace RCU 0.15.4
Tue, 4 Nov 2025 15:17:17 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #13099
[RELEASE] LTTng-modules 2.13.22 and 2.14.3 (Linux kernel tracer)
Fri, 17 Oct 2025 12:08:27 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13098
Re: Call stack context for user space trace points
Mon, 6 Oct 2025 10:22:34 -0700
Christophe Bédard via lttng-dev <[email protected]> • #13097
[RELEASE] LTTng-modules 2.13.21 and 2.14.2 (Linux kernel tracer)
Mon, 6 Oct 2025 11:50:55 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13096
Call stack context for user space trace points
Mon, 6 Oct 2025 02:50:20 +0000
"Sunku, Sai via lttng-dev" <[email protected]> • #13095
أفضل 10 مواقع للبحث عن عمل في المغرب (2025)
Fri, 26 Sep 2025 18:58:19 +0100
Rabha hssni via lttng-dev <[email protected]> • #13094
Re: URCU feature request?
Fri, 19 Sep 2025 22:42:05 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13093
Re: URCU feature request?
Fri, 19 Sep 2025 22:39:11 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13092
[RELEASE] LTTng-modules 2.13.20 and 2.14.1 (Linux kernel tracer)
Mon, 8 Sep 2025 16:07:55 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13091
Re: URCU feature request?
Sun, 07 Sep 2025 20:10:57 -0400
Olivier Dion via lttng-dev <[email protected]> • #13090
Re: URCU feature request?
Sun, 7 Sep 2025 21:18:46 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13089
Re: URCU feature request?
Fri, 05 Sep 2025 14:04:21 -0400
Olivier Dion via lttng-dev <[email protected]> • #13088
Re: URCU feature request?
Thu, 4 Sep 2025 20:09:03 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13087
Re: URCU feature request?
Thu, 4 Sep 2025 20:06:26 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13086
Re: URCU feature request?
Tue, 02 Sep 2025 21:35:16 -0400
Olivier Dion via lttng-dev <[email protected]> • #13085
Re: URCU feature request?
Tue, 2 Sep 2025 18:20:32 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13084
Re: URCU feature request?
Tue, 2 Sep 2025 23:48:43 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13083
Re: URCU feature request?
Tue, 2 Sep 2025 23:33:50 +0200
Ondřej Surý via lttng-dev <[email protected]> • #13082
Re: URCU feature request?
Tue, 2 Sep 2025 23:06:08 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13081
Re: URCU feature request?
Tue, 2 Sep 2025 13:33:28 -0700
"Paul E. McKenney via lttng-dev" <[email protected]> • #13080
Re: URCU feature request?
Tue, 2 Sep 2025 16:24:16 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13079
Re: URCU feature request?
Tue, 2 Sep 2025 16:17:19 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13078
Re: URCU feature request?
Tue, 2 Sep 2025 16:02:28 +0200
Thobias Knudsen via lttng-dev <[email protected]> • #13077
Re: [PATCH] eventfd.cpp: Remove the scope resolution operator
Mon, 18 Aug 2025 15:16:30 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13076
Fwd: tests/regression/tools/clear/test_ust fails occacionally
Thu, 17 Jul 2025 10:17:27 +0800
"Yu, Mingli via lttng-dev" <[email protected]> • #13075
Re: tests/regression/tools/clear/test_ust fails occacionally
Thu, 17 Jul 2025 10:10:35 +0800
"Yu, Mingli via lttng-dev" <[email protected]> • #13074
[PATCH] eventfd.cpp: Remove the scope resolution operator
Thu, 24 Jul 2025 14:35:51 +0800
"mingli.yu--- via lttng-dev" <[email protected]> • #13073
Adding new events / streams to an existing trace?
Mon, 21 Jul 2025 23:21:48 -0700
Alec Rivers via lttng-dev <[email protected]> • #13072
[RELEASE] Babeltrace 2.0.7 - Amqui
Tue, 22 Jul 2025 17:40:24 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13071
[RELEASE] Babeltrace 2.1.2 - Brossard
Tue, 22 Jul 2025 17:38:48 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13070
Re: Integrating QSBR with libuv
Tue, 22 Jul 2025 10:05:25 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13069
Re: tests/regression/tools/clear/test_ust fails occacionally
Tue, 22 Jul 2025 09:58:20 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13068
Re: tests/regression/tools/clear/test_ust fails occacionally
Thu, 17 Jul 2025 10:27:07 +0800
"Yu, Mingli via lttng-dev" <[email protected]> • #13067
Integrating QSBR with libuv
Wed, 16 Jul 2025 06:09:22 +0200
Ondřej Surý via lttng-dev <[email protected]> • #13066
tests/regression/tools/clear/test_ust fails occacionally
Mon, 14 Jul 2025 17:37:56 +0800
"Yu, Mingli via lttng-dev" <[email protected]> • #13065
Re: cds_lfht_new() clarification - init vs min
Thu, 10 Jul 2025 16:40:29 +0200
Ondřej Surý via lttng-dev <[email protected]> • #13064
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.