org.lttng.lists.lttng-dev archive

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

Re: cds_lfht_new() clarification - init vs min
Thu, 10 Jul 2025 10:05:13 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13063
cds_lfht_new() clarification - init vs min
Wed, 9 Jul 2025 20:57:31 +0200
Ondřej Surý via lttng-dev <[email protected]> • #13062
[RELEASE] LTTng 2.14.0 - Orbitales - Linux kernel and user space tracer
Fri, 27 Jun 2025 15:50:10 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13061
Re: Malformed Tracefiles
Thu, 26 Jun 2025 10:22:18 +0200
Georg Muck via lttng-dev <[email protected]> • #13060
Re: Method to get LTTNG-UST version during runtime?
Wed, 25 Jun 2025 17:15:38 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13059
Re: Malformed Tracefiles
Wed, 25 Jun 2025 16:52:08 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13058
Re: Malformed Tracefiles
Wed, 25 Jun 2025 11:49:56 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13057
Re: Method to get LTTNG-UST version during runtime?
Mon, 23 Jun 2025 21:04:42 +0200
Norbert Lange via lttng-dev <[email protected]> • #13056
Re: Malformed Tracefiles
Mon, 23 Jun 2025 10:26:44 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13055
Re: Method to get LTTNG-UST version during runtime?
Mon, 23 Jun 2025 10:21:05 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13054
Re: lttng-tools-2.14.0-rc1: ODR violation
Fri, 20 Jun 2025 12:08:05 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13053
Malformed Tracefiles
Thu, 19 Jun 2025 16:58:59 +0200
Georg Muck via lttng-dev <[email protected]> • #13052
Method to get LTTNG-UST version during runtime?
Wed, 18 Jun 2025 17:22:16 +0200
Norbert Lange via lttng-dev <[email protected]> • #13051
Re: lttng-tools-2.14.0-rc1: Not possible to disable babeltrace2 dependency
Tue, 17 Jun 2025 14:28:45 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13050
Re: lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Tue, 17 Jun 2025 13:29:07 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13049
Re: lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Tue, 17 Jun 2025 17:08:58 +0200
Norbert Lange via lttng-dev <[email protected]> • #13048
Re: lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Tue, 17 Jun 2025 10:50:10 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13047
Re: [lttng-dev] Feature request: dynamically load from prefix
Tue, 17 Jun 2025 16:19:23 +0200
Norbert Lange via lttng-dev <[email protected]> • #13046
Re: lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Tue, 17 Jun 2025 10:19:04 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13045
Re: lttng-tools-2.14.0-rc1: Not possible to disable babeltrace2 dependency
Tue, 17 Jun 2025 16:18:31 +0200
Norbert Lange via lttng-dev <[email protected]> • #13044
lttng-tools-2.14.0-rc1: fails to compile with libxml2-2.14.4
Tue, 17 Jun 2025 16:15:30 +0200
Norbert Lange via lttng-dev <[email protected]> • #13043
Re: lttng-tools-2.14.0-rc1: Not possible to disable babeltrace2 dependency
Tue, 17 Jun 2025 10:13:02 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13042
lttng-tools-2.14.0-rc1: ODR violation
Tue, 17 Jun 2025 13:00:44 +0200
Norbert Lange via lttng-dev <[email protected]> • #13041
lttng-tools-2.14.0-rc1: Not possible to disable babeltrace2 dependency
Tue, 17 Jun 2025 12:54:51 +0200
Norbert Lange via lttng-dev <[email protected]> • #13040
Re: A question regarding isolated cpus and software interrupts
Tue, 17 Jun 2025 12:52:01 +0200
Norbert Lange via lttng-dev <[email protected]> • #13039
[RELEASE] LTTng-modules 2.13.19 (Linux kernel tracer)
Tue, 10 Jun 2025 15:07:47 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13038
Re: [PATCH urcu] src/urcu-bp.c: assert => urcu_posix_assert
Mon, 9 Jun 2025 11:41:36 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13037
[PATCH urcu] src/urcu-bp.c: assert => urcu_posix_assert
Mon, 9 Jun 2025 10:49:23 +0800
Zhixu Liu via lttng-dev <[email protected]> • #13036
Re: Function tracing not working
Fri, 6 Jun 2025 14:14:25 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13035
Re: Function tracing not working
Fri, 6 Jun 2025 15:37:50 +0100
David Aldrich via lttng-dev <[email protected]> • #13034
Re: Function tracing not working
Thu, 5 Jun 2025 14:49:13 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13033
Re: Function tracing not working
Thu, 5 Jun 2025 11:49:26 +0100
David Aldrich via lttng-dev <[email protected]> • #13032
Re: Function tracing not working
Wed, 4 Jun 2025 17:22:35 +0100
David Aldrich via lttng-dev <[email protected]> • #13031
Re: LTTng kernel tracer writes packetized (binary) metadata instead of plain text on Ubuntu 22.04 5.15.0-140/141-generic with LTTng 2.13.18
Wed, 4 Jun 2025 12:07:18 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13030
LTTng kernel tracer writes packetized (binary) metadata instead of plain text on Ubuntu 22.04 5.15.0-140/141-generic with LTTng 2.13.18
Wed, 4 Jun 2025 05:00:59 +0000
Shreya Tripathi via lttng-dev <[email protected]> • #13029
Re: Function tracing not working
Mon, 2 Jun 2025 13:22:55 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13028
Function tracing not working
Mon, 2 Jun 2025 15:37:30 +0100
David Aldrich via lttng-dev <[email protected]> • #13027
Re: A question regarding isolated cpus and software interrupts
Fri, 30 May 2025 16:00:23 +0100
David Aldrich via lttng-dev <[email protected]> • #13026
Re: A question regarding isolated cpus and software interrupts
Fri, 30 May 2025 10:49:20 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13025
A question regarding isolated cpus and software interrupts
Thu, 29 May 2025 19:06:31 +0100
David Aldrich via lttng-dev <[email protected]> • #13024
Re: lttng-modules-2.13.18 Condition for Kernel 5.14.0-582.el9.x86_64 of Centos Stream 9.
Wed, 14 May 2025 15:57:38 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13023
[RELEASE] LTTng-modules 2.14.0-rc2 (Linux kernel tracer)
Wed, 14 May 2025 15:53:55 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13022
[RELEASE] LTTng-UST 2.14.0-rc2 (Linux user-space tracer)
Wed, 14 May 2025 15:41:43 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13021
[RELEASE] Userspace RCU 0.15.3
Wed, 14 May 2025 15:30:47 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13020
lttng-modules-2.13.18 Condition for Kernel 5.14.0-582.el9.x86_64 of Centos Stream 9.
Wed, 14 May 2025 19:16:23 +0000
Jean-Marc Chevalier via lttng-dev <[email protected]> • #13019
Re: Problems with arrays of floats (lttng 2.13)
Tue, 13 May 2025 17:40:09 +0200 (CEST)
Herman Bruyninckx via lttng-dev <[email protected]> • #13018
Re: Problems with arrays of floats (lttng 2.13)
Tue, 13 May 2025 10:38:56 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13017
Re: Understanding SOFT IRQ 1
Mon, 12 May 2025 11:41:44 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13016
Re: Understanding SOFT IRQ 1
Mon, 12 May 2025 11:18:42 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13015
Re: Problems with arrays of floats (lttng 2.13)
Sat, 10 May 2025 10:14:10 +0200 (CEST)
Herman Bruyninckx via lttng-dev <[email protected]> • #13014
Understanding SOFT IRQ 1
Fri, 9 May 2025 17:00:17 +0100
David Aldrich via lttng-dev <[email protected]> • #13013
Re: Problems with arrays of floats (lttng 2.13)
Fri, 9 May 2025 11:10:38 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13012
Problems with arrays of floats (lttng 2.13)
Fri, 9 May 2025 12:03:23 +0200 (CEST)
Herman Bruyninckx via lttng-dev <[email protected]> • #13011
Re: Not capturing ust events
Thu, 8 May 2025 18:59:45 +0100
David Aldrich via lttng-dev <[email protected]> • #13010
Re: Not capturing ust events
Thu, 8 May 2025 18:02:12 +0100
David Aldrich via lttng-dev <[email protected]> • #13009
Re: Not capturing ust events
Thu, 8 May 2025 13:25:08 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13008
Re: Not capturing ust events
Thu, 8 May 2025 09:51:24 -0400
Kienan Stewart via lttng-dev <[email protected]> • #13007
Not capturing ust events
Wed, 7 May 2025 17:50:33 +0100
David Aldrich via lttng-dev <[email protected]> • #13006
Fwd: Tracing Summit 2025 - Announcement and CFP
Fri, 2 May 2025 16:08:46 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13005
[RELEASE] LTTng 2.14.0-rc1 - Orbitales - Linux kernel and user space tracer
Wed, 16 Apr 2025 18:08:27 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13004
[RELEASE] Babeltrace 2.1.1 - Brossard
Mon, 14 Apr 2025 17:39:53 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13003
[RELEASE] LTTng-modules 2.13.18 (Linux kernel tracer)
Mon, 14 Apr 2025 17:36:09 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13002
[RELEASE] LTTng-UST 2.13.9 (Linux user-space tracer)
Mon, 14 Apr 2025 16:51:40 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #13001
[RELEASE] LTTng-tools 2.1 3.15 - Nordicité
Mon, 14 Apr 2025 14:50:32 -0400
Jérémie Galarneau via lttng-dev <[email protected]> • #13000
[RELEASE] Userspace RCU 0.15.2
Mon, 14 Apr 2025 11:01:26 -0400
Mathieu Desnoyers via lttng-dev <[email protected]> • #12999
Re: LTTNG Session daemon is crashing when i launch lttng
Wed, 2 Apr 2025 10:36:33 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12998
LTTNG Session daemon is crashing when i launch lttng
Wed, 2 Apr 2025 03:41:08 +0000
Deemanth P J via lttng-dev <[email protected]> • #12997
Re: lttng-dev Digest, Vol 203, Issue 7
Fri, 21 Mar 2025 10:10:44 -0400
Olivier Dion via lttng-dev <[email protected]> • #12996
Re: lttng-dev Digest, Vol 203, Issue 7
Fri, 21 Mar 2025 09:14:17 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12995
Re: lttng-dev Digest, Vol 203, Issue 7
Fri, 21 Mar 2025 18:22:52 +0530
Gour DEV via lttng-dev <[email protected]> • #12994
Re: lttng-dev Digest, Vol 203, Issue 7
Thu, 20 Mar 2025 16:51:42 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12993
Re: lttng-dev Digest, Vol 203, Issue 7
Mon, 17 Mar 2025 11:59:58 +0530
Gour DEV via lttng-dev <[email protected]> • #12992
Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Wed, 12 Mar 2025 10:36:28 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12991
Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Wed, 12 Mar 2025 14:49:07 +0530
Gour DEV via lttng-dev <[email protected]> • #12990
Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Tue, 11 Mar 2025 14:55:21 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12989
Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Tue, 11 Mar 2025 09:55:14 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12988
Memory Consumption High After Upgrading to 2.13 from 2.10
Tue, 11 Mar 2025 16:05:45 +0530
Gour DEV via lttng-dev <[email protected]> • #12987
Re: Github Action Runners creating world-writable shared memory section: lttng-ust-wait-n
Mon, 10 Mar 2025 13:36:59 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12986
Re: Memory Consumption High After Upgrading to 2.13 from 2.10
Mon, 10 Mar 2025 11:40:39 -0400
Kienan Stewart via lttng-dev <[email protected]> • #12985
Memory Consumption High After Upgrading to 2.13 from 2.10
Mon, 10 Mar 2025 19:32:18 +0530
Gour DEV via lttng-dev <[email protected]> • #12984
Re:Re: need help for avoiding system calls while using URCU (Userspace RCU)
Sat, 8 Mar 2025 17:16:46 +0800 (CST)
方锴 via lttng-dev <[email protected]> • #12983
Re:Re: need help for avoiding system calls while using URCU (Userspace RCU)
Sat, 8 Mar 2025 17:18:08 +0800 (CST)
方锴 via lttng-dev <[email protected]> • #12982
Github Action Runners creating world-writable shared memory section: lttng-ust-wait-n
Mon, 10 Mar 2025 10:12:23 -0400
bill robertson via lttng-dev <[email protected]> • #12981
Re: need help for avoiding system calls while using URCU (Userspace RCU)
Thu, 6 Mar 2025 11:58:21 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12980
Re: need help for avoiding system calls while using URCU (Userspace RCU)
Thu, 6 Mar 2025 11:17:34 -0500
Kienan Stewart via lttng-dev <[email protected]> • #12979
need help for avoiding system calls while using URCU (Userspace RCU)
Tue, 4 Mar 2025 16:09:36 +0800 (CST)
方锴 via lttng-dev <[email protected]> • #12978
[RELEASE] Userspace RCU 0.15.1
Tue, 18 Feb 2025 10:51:14 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12977
Re: librseq memory allocator portability
Mon, 3 Feb 2025 15:55:57 +0100
Mathieu Desnoyers via lttng-dev <[email protected]> • #12976
Re: librseq memory allocator portability
Mon, 3 Feb 2025 15:52:46 +0100
Mathieu Desnoyers via lttng-dev <[email protected]> • #12975
librseq memory allocator portability
Sun, 2 Feb 2025 16:48:44 +0100
Ondřej Surý via lttng-dev <[email protected]> • #12974
[RELEASE] LTTng-modules 2.13.17 (Linux kernel tracer)
Fri, 24 Jan 2025 15:54:55 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12973
[RELEASE] Babeltrace 2.1.0
Wed, 22 Jan 2025 23:45:05 -0500
Jérémie Galarneau via lttng-dev <[email protected]> • #12972
Re: [PATCH] lttng-modules fix for RHEL 9.5 kernels
Wed, 22 Jan 2025 08:08:52 -0500
Martin Hicks via lttng-dev <[email protected]> • #12971
Re: [PATCH] lttng-modules fix for RHEL 9.5 kernels
Tue, 21 Jan 2025 14:56:28 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12970
[PATCH] lttng-modules fix for RHEL 9.5 kernels
Wed, 15 Jan 2025 09:23:00 -0500
Martin Hicks via lttng-dev <[email protected]> • #12969
Re: Tracing Ceph with LTTng-UST issue
Mon, 6 Jan 2025 11:33:09 -0500
Kienan Stewart via lttng-dev <[email protected]> • #12968
Tracing Ceph with LTTng-UST issue
Thu, 2 Jan 2025 23:14:16 +0100
Lina SADI via lttng-dev <[email protected]> • #12967
Re: [RELEASE] Userspace RCU 0.15.0
Sat, 21 Dec 2024 11:22:40 -0500
Olivier Dion via lttng-dev <[email protected]> • #12966
Re: [RELEASE] Userspace RCU 0.15.0
Fri, 20 Dec 2024 13:45:16 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12965
[RELEASE] Userspace RCU 0.15.0
Fri, 20 Dec 2024 12:25:17 -0500
Mathieu Desnoyers via lttng-dev <[email protected]> • #12964
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.