#################################################################### # Copyright (c) 2012, 2015 Ericsson # # All rights reserved. This program and the accompanying materials are # made available under the terms of the Eclipse Public License v1.0 which # accompanies this distribution, and is available at # http://www.eclipse.org/legal/epl-v10.html # # Contributors: # Bernd Hufmann - Initial API and implementation #################################################################### #################################################################### # Scenario: Test lttng not installed #################################################################### LttngNotInstalled lttng list 1 Command not found #################################################################### # Scenario: Test lttng version #################################################################### LttngVersion lttng version 0 lttng version 2.1.0 - Basse Messe Web site: http://lttng.org/ lttng is free software and under the GPL license and part LGPL #################################################################### # Scenario: Test lttng version # output with prompt #################################################################### LttngVersionWithPrompt lttng version 0 Prompt> lttng version 2.0.0 - Annedd'ale Web site: http://lttng.org/ lttng is free software and under the GPL license and part LGPL #################################################################### # Scenario: Test lttng version (unsupported version) #################################################################### LttngUnsupportedVersion lttng version 0 lttng version 200.0.0 - Annedd'ale Web site: http://lttng.org/ lttng is free software and under the GPL license and part LGPL #################################################################### # Scenario: Test lttng version (noversion) #################################################################### LttngNoVersion lttng version 0 Web site: http://lttng.org/ lttng is free software and under the GPL license and part LGPL #################################################################### # Scenario: Test lttng version (compiled from source) #################################################################### LttngVersionCompiled lttng version 0 lttng version heads/stable-2.5-0-g3910e60 - Fumisterie The Fumisterie is a beer whose style is at the confluence of English and German ales. On the palate, it is full-bodied, malty and slightly caramelized. The organic hemp seeds incorporated during the brewing gives it a unique and original taste. The hop flavour comes through delicately in the after taste. Web site: http://lttng.org lttng is free software and under the GPL license and part LGPL #################################################################### # Scenario: Test no sessions available #################################################################### NoSessionAvailable lttng list 0 Currently no available tracing session #################################################################### # Scenario: Test get sessions #################################################################### GetSessionNames1 lttng list 0 Available tracing sessions: 1) mysession1 (/home/user/lttng-traces/mysession1-20120123-083928) [inactive] 2) mysession (/home/user/lttng-traces/mysession-20120123-083318) [inactive] Use lttng list for more details #################################################################### # Scenario: Test get sessions with tracing group #################################################################### GetSessionWithTracingGroup lttng -g group list 0 Available tracing sessions: 1) mysession1 (/home/user/lttng-traces/mysession1-20120123-083928) [inactive] 2) mysession (/home/user/lttng-traces/mysession-20120123-083318) [inactive] Use lttng list for more details #################################################################### # Scenario: Test lttng list where session doesn't exist #################################################################### GetSessionNameNotExist lttng list test 1 Session test not found Error: Session name not found #################################################################### # Scenario: Test lttng -vvv list where session doesn't exist #################################################################### GetSessionNameNotExistVerbose lttng -vvv list test 1 DEBUG2: Session name: test [in cmd_list() at commands/list.c:618] DEBUG1: Session count 1 [in list_sessions() at commands/list.c:485] Error: Session 'test' not found Error: Command error DEBUG1: Clean exit [in clean_exit() at lttng.c:165] #################################################################### # Scenario: Test lttng list with garbage output #################################################################### GetSessionGarbageOut lttng list 0 asdfaereafsdcv 12333456434&*89**(())(^%$* @#$%^&*()@#$%^&*()0834523094578kj;djkfs a;sdf094v5u dsafj;sd9 #################################################################### # Scenario: Test lttng list with sample outputs #################################################################### GetSession1 lttng list mysession 0 Tracing session mysession: [active] Trace path: /home/user/lttng-traces/mysession-20120129-084256 === Domain: Kernel === Channels: ------------- - channel0: [enabled] Attributes: overwrite mode: 0 subbufers size: 262144 number of subbufers: 4 switch timer interval: 0 read timer interval: 200 output: splice() Events: block_rq_remap (loglevel: TRACE_EMERG (0)) (type: tracepoint) [enabled] block_bio_remap (loglevel: TRACE_EMERG (0)) (type: tracepoint) [disabled] - channel1: [disabled] Attributes: overwrite mode: 1 subbufers size: 524288 number of subbufers: 4 switch timer interval: 100 read timer interval: 400 output: splice() Events: None === Domain: UST global === Channels: ------------- - mychannel1: [disabled] Attributes: overwrite mode: 1 subbufers size: 8192 number of subbufers: 8 switch timer interval: 200 read timer interval: 100 output: mmap() Events: None - channel0: [enabled] Attributes: overwrite mode: 0 subbufers size: 4096 number of subbufers: 4 switch timer interval: 0 read timer interval: 200 output: mmap() Events: ust_tests_hello:tptest_sighandler (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint) [disabled] * (type: tracepoint) [enabled] lttng list mysession1 0 Tracing session mysession1: [inactive] Trace path: /home/user/lttng-traces/mysession1-20120203-133225 #################################################################### # Scenario: Test lttng list (with live time interval) #################################################################### GetSessionWithLiveInterval lttng list mysession 0 Tracing session mysession: [inactive snapshot] Trace path: Live timer interval (usec): 4294967295 #------------------------------------------------------------------------------ lttng snapshot list-output -s mysession 0 Snapshot output list for session mysession [1] snapshot-1: /home/user/lttng-traces/mysession-20120129-084256 (max-size: 0) #------------------------------------------------------------------------------ lttng list mysession1 0 Tracing session mysession1: [active] Trace path: /home/user/lttng-traces/mysession1-20120129-084256 Live timer interval (usec): 0 #------------------------------------------------------------------------------ lttng list mysession2 0 Tracing session mysession2: [inactive] Trace path: tcp4://172.0.0.1:5342/ [data: 5343] Live timer interval (usec): 1000000 #################################################################### # Scenario: Test "lttng list -k" with sample output #################################################################### GetKernelProvider1 lttng list -k 0 Kernel events ------------- sched_kthread_stop (loglevel: TRACE_EMERG (0)) (type: tracepoint) sched_kthread_stop_ret (loglevel: TRACE_EMERG (0)) (type: tracepoint) sched_wakeup_new (loglevel: TRACE_EMERG (0)) (type: tracepoint) #################################################################### # Scenario: Test "lttng list -k" with no kernel and no session daemon #################################################################### ListWithNoKernel1 lttng list -k 1 Spawning session daemon Error: Unable to list kernel events #################################################################### # Scenario: Test "lttng list -k" with no kernel and with session daemon #################################################################### ListWithNoKernel2 lttng list -k 1 Error: Unable to list kernel events #################################################################### # Scenario: Test "lttng list -k" with no kernel, with session daemon and verbose #################################################################### ListWithNoKernelVerbose lttng -vvv list -k 1 DEBUG2: Session name: (null) [in cmd_list() at commands/list.c:618] DEBUG1: Getting kernel tracing events [in list_kernel_events() at commands/list.c:309] Error: Unable to list kernel events DEBUG1: Clean exit [in clean_exit() at lttng.c:165] #################################################################### # Scenario: Test "lttng list -u" with sample output #################################################################### GetUstProvider1 lttng list -u 0 UST events: ------------- PID: 9379 - Name: /home/user/git/lttng-ust/tests/hello.cxx/.libs/lt-hello ust_tests_hello:tptest_sighandler (loglevel: TRACE_DEBUG_MODULE (10)) (type: tracepoint) ust_tests_hello:tptest (loglevel: TRACE_INFO (6)) (type: tracepoint) PID: 4852 - Name: /home/user/git/lttng-ust/tests/hello.cxx/.libs/lt-hello ust_tests_hello:tptest_sighandler (loglevel: TRACE_WARNING (4)) (type: tracepoint) ust_tests_hello:tptest (loglevel: TRACE_DEBUG_FUNCTION (12)) (type: tracepoint) #################################################################### # Scenario: Test "lttng list -u" with no UST provider available #################################################################### GetUstProvider2 lttng list -u 0 UST events: ------------- None #################################################################### # Scenario: Test "lttng list -u" with no UST available (LTTng 2.0.x) #################################################################### ListWithNoUst1 lttng list -u 1 UST events: ------------- None Segmentation Fault #################################################################### # Scenario: Test "lttng list -u" with no UST available and no session daemon #################################################################### ListWithNoUst2 lttng list -u -f 1 Spawning a session daemon Error: Unable to list UST events: Listing UST events failed Error: Command Error #################################################################### # Scenario: Test "lttng list -u" with no ust and with session daemon #################################################################### ListWithNoUst3 lttng list -u -f 1 Error: Unable to list UST events: Listing UST events failed Error: Command Error #################################################################### # Scenario: Test "lttng list -u" with no kernel, with session daemon and verbose #################################################################### ListWithNoUstVerbose lttng -vvv list -u -f 1 DEBUG2: Session name: (null) [in cmd_list() at commands/list.c:618] DEBUG1: Getting kernel tracing events [in list_kernel_events() at commands/list.c:309] Spawning a session daemon Error: Unable to list UST events: Listing UST events failed Error: Command Error DEBUG1: Clean exit [in clean_exit() at lttng.c:165] #################################################################### # Scenario: Test "lttng list -u -f" with sample output (version 2.1.0) #################################################################### GetUstProvider3 lttng list -u -f 0 UST events: ------------- PID: 9379 - Name: /home/user/git/lttng-ust/tests/hello.cxx/.libs/lt-hello ust_tests_hello:tptest_sighandler (loglevel: TRACE_DEBUG_MODULE (10)) (type: tracepoint) ust_tests_hello:tptest (loglevel: TRACE_INFO (6)) (type: tracepoint) field: doublefield (float) field: floatfield (float) field: stringfield (string) PID: 4852 - Name: /home/user/git/lttng-ust/tests/hello.cxx/.libs/lt-hello ust_tests_hello:tptest_sighandler (loglevel: TRACE_WARNING (4)) (type: tracepoint) ust_tests_hello:tptest (loglevel: TRACE_DEBUG_FUNCTION (12)) (type: tracepoint) field: doublefield (float) field: floatfield (float) field: stringfield (string) #################################################################### # Scenario: Test "lttng create #################################################################### CreateSession1 lttng create mysession2 0 Session mysession2 created. Traces will be written in /home/user/lttng-traces/mysession2-20120209-095418 #################################################################### # Scenario: Test "lttng create #################################################################### CreateSessionWithPrompt lttng create mysession2 0 Prompt> Session mysession2 created. Traces will be written in /home/user/lttng-traces/mysession2-20120209-095418 #################################################################### # Scenario: Test "lttng create with different variants # and errors #################################################################### CreateSessionVariants lttng create alreadyExist 1 Error: Session name already exist lttng create session with spaces 0 Session session with spaces created. Traces will be written in /home/user/lttng-traces/session with spaces-20120209-095418 lttng create wrongName 0 Session auto created. Traces will be written in /home/user/lttng-traces/auto-20120209-095418 lttng create wrongPath -o /home/user/hallo 0 Session wrongPath created. Traces will be written in /home/user/lttng-traces/wrongPath-20120209-095418 lttng create pathWithSpaces -o /home/user/hallo user/here 0 Session pathWithSpaces created. Traces will be written in /home/user/hallo user/here/pathWithSpaces-20120209-095418 #################################################################### # Scenario: Test "lttng destroy #################################################################### DestroySession1 lttng destroy mysession2 0 Session mysession2 destroyed. #################################################################### # Scenario: Test "lttng -vvv destroy " #################################################################### DestroySessionVerbose lttng -vvv destroy mysession2 0 DEBUG2: Config file path found: /home/eedbhu [in get_session_name() at utils.c:98] DEBUG1: Session name found: mysession2 [in get_session_name() at utils.c:99] Session mysession2 destroyed at /home/eedbhu #################################################################### # Scenario: Test "lttng enable-channel ..." with different inputs #################################################################### ChannelHandling lttng enable-channel mychannel0,mychannel1 -k -s mysession2 --overwrite --subbuf-size 16384 --num-subbuf 2 --switch-timer 200 --read-timer 100 -C 0 -W 10 0 Kernel channel mychannel0 enabled for session mysession2 Kernel channel mychannel1 enabled for session mysession2 lttng enable-channel mychannel0,mychannel1 -k -s mysession2 --overwrite --subbuf-size 16384 --num-subbuf 2 --switch-timer 200 --read-timer 100 0 Kernel channel mychannel0 enabled for session mysession2 Kernel channel mychannel1 enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 --overwrite --subbuf-size 32768 --num-subbuf 1 --switch-timer 100 --read-timer 200 -C 0 -W 20 0 UST channel channel0 enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 --overwrite --subbuf-size 32768 --num-subbuf 1 --switch-timer 100 --read-timer 200 0 UST channel channel0 enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 --overwrite --subbuf-size 32768 --num-subbuf 1 --switch-timer 100 --read-timer 200 --buffers-uid -C 0 -W 20 0 UST channel channel0 enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 --overwrite --buffers-pid 0 UST channel ustChannel enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 --overwrite --subbuf-size 32768 --num-subbuf 1 --switch-timer 100 --read-timer 200 --buffers-uid 0 UST channel channel0 enabled for session mysession2 lttng enable-channel mychannel0,mychannel1 -k -s mysession2 0 Kernel channel mychannel0 enabled for session mysession2 Kernel channel mychannel1 enabled for session mysession2 lttng enable-channel ustChannel -u -s mysession2 0 UST channel mychannel0 enabled for session mysession2 lttng disable-channel mychannel0,mychannel1 -k -s mysession2 0 Kernel channel mychannel0 disabled for session mysession2 Kernel channel mychannel1 disabled for session mysession2 lttng disable-channel ustChannel -u -s mysession2 0 UST channel mychannel0 enabled for session mysession2 #################################################################### # Scenario: Test "lttng enable-events ..." with different inputs #################################################################### EventHandling # Tracepoint test cases lttng enable-event block_rq_remap,block_bio_remap,softirq_entry -k -s mysession2 --tracepoint 0 kernel event block_rq_remap created in channel channel0 kernel event block_bio_remap created in channel channel0 kernel event softirq_entry created in channel channel0 lttng enable-event -a -k -s mysession2 -c mychannel --tracepoint 0 All kernel tracepoints are enabled in channel channel0 lttng enable-event ust_tests_hello:tptest_sighandler -u -s mysession2 -c mychannel --tracepoint 0 UST event ust_tests_hello:tptest_sighandler created in channel mychannel lttng enable-event ust_tests_hello:tptest_sighandler -u -s mysession2 -c mychannel --tracepoint --filter intfield==10 0 UST event ust_tests_hello:tptest_sighandler created in channel mychannel lttng enable-event -a -u -s mysession2 -c mychannel --tracepoint 0 All UST tracepoints are enabled in channel mychannel # Syscall test cases lttng enable-event -a -k -s mysession2 --syscall 0 All kernel system calls are enabled in channel channel0 lttng enable-event -a -k -s mysession2 -c mychannel --syscall 0 All kernel system calls are enabled in channel mychannel # dynamic probe/function probe test cases lttng enable-event myevent0 -k -s mysession2 --function 0xc0101340 0 kernel event myevent0 created in channel mychannel lttng enable-event myevent1 -k -s mysession2 -c mychannel --probe init_post 0 kernel event myevent1 created in channel mychannel # log level test cases lttng enable-event myevent4 -u -s mysession2 --loglevel-only TRACE_DEBUG 0 UST event myevent4 created in channel channel0 lttng enable-event myevent5 -u -s mysession2 -c mychannel --loglevel TRACE_DEBUG_FUNCTION 0 UST event myevent5 created in channel mychannel #################################################################### # Scenario: Test "lttng add-context -h" and lttng add-context ..." with different inputs #################################################################### ContextHandling lttng add-context -h 0 usage: lttng add-context -t TYPE If no channel and no event is given (-c/-e), the context will be added to all events and all channels. Otherwise the context will be added only to the channel (-c) and/or event (-e) indicated. Exactly one domain (-k/--kernel or -u/--userspace) must be specified. Options: -h, --help Show this help --list-options Simple listing of options -s, --session NAME Apply to session name -c, --channel NAME Apply to channel -e, --event NAME Apply to event -k, --kernel Apply to the kernel tracer -u, --userspace Apply to the user-space tracer -t, --type TYPE Context type. You can repeat that option on the command line to specify multiple contexts at once. (--kernel preempts --userspace) TYPE can be one of the strings below: pid, procname, prio, nice, vpid, tid, pthread_id, vtid, ppid, vppid, perf:cpu-cycles, perf:cycles Example: This command will add the context information 'prio' and two perf counters (hardware branch misses and cache misses), to all events in the trace data output: # lttng add-context -k -t prio -t perf:branch-misses -t perf:cache-misses lttng add-context -s mysession2 -c mychannel -e ust_tests_hello:tptest_sighandler -u -t prio -t pid 0 UST context prio added to event ust_tests_hello:tptest_sighandle channel mychannel UST context pid added to event sched_kthread_stop_ret channel mychannel ContextErrorHandling lttng add-context -h 1 usage: lttng add-context -t TYPE If no channel and no event is given (-c/-e), the context will be added to all events and all channels. Otherwise the context will be added only to the channel (-c) and/or event (-e) indicated. Exactly one domain (-k/--kernel or -u/--userspace) must be specified. Options: -h, --help Show this help --list-options Simple listing of options -s, --session NAME Apply to session name -c, --channel NAME Apply to channel -e, --event NAME Apply to event -k, --kernel Apply to the kernel tracer -u, --userspace Apply to the user-space tracer -t, --type TYPE Context type. You can repeat that option on the command line to specify multiple contexts at once. (--kernel preempts --userspace) TYPE can be one of the strings below: pid, procname, prio, nice, vpid, tid, pthread_id, vtid, ppid, vppid, perf:cpu-cycles, perf:cycles Example: This command will add the context information 'prio' and two perf counters (hardware branch misses and cache misses), to all events in the trace data output: # lttng add-context -k -t prio -t perf:branch-misses -t perf:cache-misses lttng add-context -s mysession2 -c mychannel -e ust_tests_hello:tptest_sighandler -u -t prio -t pid 1 UST context prio added to event ust_tests_hello:tptest_sighandle channel mychannel UST context pid added to event sched_kthread_stop_ret channel mychannel #################################################################### # Scenario: Test "lttng create with LTTng 2.1 options #################################################################### CreateSessionLttng2.1 lttng create mysession -U net://172.0.0.1 0 Session mysession created. Traces will be written in net://172.0.0.1 lttng create mysession -U file:///tmp 0 Session mysession created. Traces will be written in file:///tmp lttng create mysession -C tcp://172.0.0.1 -D tcp://172.0.0.1:5343 0 Session mysession created. Control URL tcp://172.0.0.1 set for session mysession Data URL tcp://172.0.0.1:5343 set for session mysession lttng create mysession -U net://172.0.0.1:1234:2345 0 Session mysession created. Traces will be written in net://172.0.0.1:1234:2345 lttng destroy mysession 0 Session mysession destroyed. lttng -vvv create mysession -U net://172.0.0.1 0 DEBUG3: URI string: net://172.0.0.1 [in uri_parse() at uri.c:253] DEBUG2: IP address resolved to 172.0.0.1 [in set_ip_address() at uri.c:132] DEBUG3: URI dtype: 1, proto: 1, host: 172.0.0.1, subdir: , ctrl: 0, data: 0 [in uri_parse() at uri.c:467] DEBUG1: LSM cmd type : 8 [in send_session_msg() at lttng-ctl.c:261] Session mysession created. Traces will be written in net://172.0.0.1 DEBUG1: Init config session in /home/bernd [in config_init() at conf.c:294] #################################################################### # Scenario: Test "lttng -vvv create with LTTng 2.1 options" #################################################################### CreateSessionLttngVerbose2.1 lttng -vvv create mysession -U net://172.0.0.1 0 DEBUG3: URI string: net://172.0.0.1 [in uri_parse() at uri.c:253] DEBUG2: IP address resolved to 172.0.0.1 [in set_ip_address() at uri.c:132] DEBUG3: URI dtype: 1, proto: 1, host: 172.0.0.1, subdir: , ctrl: 0, data: 0 [in uri_parse() at uri.c:467] DEBUG1: LSM cmd type : 8 [in send_session_msg() at lttng-ctl.c:261] Session mysession created. Traces will be written in net://172.0.0.1 DEBUG1: Init config session in /home/bernd [in config_init() at conf.c:294] lttng -vvv destroy mysession 0 Session mysession destroyed. #################################################################### # Scenario: Test "lttng create --snapshot (LTTng 2.3) #################################################################### CreateSessionSnapshot lttng create mysession --snapshot 0 Session mysession created. Default snapshot output set to: /home/user/lttng-traces/mysession-20130913-141651 Snapshot mode set. Every channel enabled for that session will be set in overwrite mode and mmap output. #------------------------------------------------------------------------------ lttng snapshot list-output -s mysession 0 Snapshot output list for session mysession [1] snapshot-1: /home/user/lttng-traces/mysession-20130913-141651 #------------------------------------------------------------------------------ lttng list 0 1) mysession () [inactive snapshot] #------------------------------------------------------------------------------ lttng snapshot record -s mysession 0 Snapshot recorded successfully for session mysession #------------------------------------------------------------------------------ lttng destroy mysession 0 Session mysession destroyed. #################################################################### # Scenario: Test "lttng create --snapshot -U (LTTng 2.3) #################################################################### CreateSessionStreamedSnapshot lttng create mysession --snapshot -U net://172.0.0.1 0 Session mysession created. Default snapshot output set to: net://172.0.0.1 Snapshot mode set. Every channel enabled for that session will be set in overwrite mode and mmap output. #------------------------------------------------------------------------------ lttng snapshot list-output -s mysession 0 Snapshot output list for session mysession [2] snapshot-2: net4://172.0.0.1:5342/ #------------------------------------------------------------------------------ lttng list 0 1) mysession () [inactive snapshot] #------------------------------------------------------------------------------ lttng snapshot record -s mysession 0 Snapshot recorded successfully for session mysession #------------------------------------------------------------------------------ lttng destroy mysession 0 Session mysession destroyed. #################################################################### # Scenario: Test "lttng create --snapshot (LTTng 2.3) #################################################################### CreateSessionSnapshotErrors lttng snapshot list-output -s blabla 1 Error: Session name not found #------------------------------------------------------------------------------ #next is not an error case but good to be tested lttng list 0 1) mysession () [active snapshot] #------------------------------------------------------------------------------ lttng snapshot record -s blabla 1 Error: Session name not found #------------------------------------------------------------------------------ lttng snapshot record -s mysession 1 Error: Session needs to be started once #################################################################### # Scenario: Test "lttng create --live [USEC] (LTTng 2.4) #################################################################### CreateSessionLive lttng create mysession --live -U net://127.0.0.1 0 Session mysession created. Traces will be written in net://127.0.0.1 Live timer set to 1000000 usec #------------------------------------------------------------------------------ lttng list 0 Available tracing sessions: 1) mysession (net4://127.0.0.1:5342/ [data: 5343]) [inactive] Use lttng list for more details #------------------------------------------------------------------------------ lttng destroy mysession 0 Session mysession destroyed. #################################################################### # Scenario: Test errors for "lttng create --live [USEC] (LTTng 2.4) #################################################################### CreateSessionLiveErrors lttng create mysession --live --snapshot 1 Error: Snapshot and live modes are mutually exclusive. Error: Command error #------------------------------------------------------------------------------ lttng create mysession --live -U blah 1 Error: URI parse unknown protocol blah Error: Unable to parse the URL blah Error: Invalid parameter #------------------------------------------------------------------------------ lttng create mysession --live -C net://127.0.0.1 1 Error: You need both control and data URL. Error: Command error #################################################################### # Scenario: Test "lttng create --snapshot (LTTng 2.5) #################################################################### CreateSessionSnapshot2.5 lttng create mysession --snapshot 0 Session mysession created. Default snapshot output set to: /home/user/lttng-traces/mysession-20130913-141651 Snapshot mode set. Every channel enabled for that session will be set in overwrite mode and mmap output. #------------------------------------------------------------------------------ lttng snapshot list-output -s mysession 0 Snapshot output list for session mysession [1] snapshot-1: /home/user/lttng-traces/mysession-20130913-141651 (max-size: 0) #------------------------------------------------------------------------------ lttng list 0 1) mysession () [inactive snapshot] #------------------------------------------------------------------------------ lttng snapshot record -s mysession 0 Snapshot recorded successfully for session mysession #----------------------------------------------------------------------------- lttng destroy mysession 0 Session mysession destroyed. #################################################################### # Scenario: Test "lttng load [OPTIONS] [SESSION]" # "lttng save [OPTIONS] [SESSION]" # (LTTng 2.5) #################################################################### SessionProfile lttng load -i /home/user/.lttng/sessions/mysession.lttng 0 All sessions have been loaded successfully. SessionProfile lttng load -i /home/user/.lttng/sessions/mysession.lttng -f 0 All sessions have been loaded successfully. lttng save 0 All sessions have been saved successfully. lttng save mysession 0 Session mysession saved successfully. lttng save -f mysession 0 Session mysession saved successfully. lttng save -o /tmp/test -f mysession 0 Session mysession saved successfully.