[lttng-dev] infinite loop invoked using lttng enable/disable-event

2013-06-25 Thread Avi Goren
Hi,
I'm using lttng 2.2.0 and encountered an infinite loop:
-
root@ubuntu:~# lttng create
Session auto-20130624-165047 created.
Traces will be written in /home/avig/lttng-traces/auto-20130624-165047
root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_ALERT
All UST events are enabled in channel channel0 for loglevel TRACE_ALERT
root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
root@ubuntu:~# lttng disable-event -a -u
All UST events are disabled in channel channel0
root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
root@ubuntu:~# lttng disable-event -a -u
(infinite loop here...)
-
I guess it's probably due to the setting of loglevel through enable-event
twice..?
Avi
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


Re: [lttng-dev] infinite loop invoked using lttng enable/disable-event

2013-06-25 Thread David Goulet
Hmmm

Can you report that on bugs.lttng.org with the session daemon logs (-vvv
--verbose-consumer) ?

If indeed the session daemon is stuck or even lttng, it's a pretty serious 
issue.

Thanks!
David

Avi Goren:
 Hi,
 I'm using lttng 2.2.0 and encountered an infinite loop:
 -
 root@ubuntu:~# lttng create
 Session auto-20130624-165047 created.
 Traces will be written in /home/avig/lttng-traces/auto-20130624-165047
 root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_ALERT
 All UST events are enabled in channel channel0 for loglevel TRACE_ALERT
 root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_CRIT
 All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
 root@ubuntu:~# lttng disable-event -a -u
 All UST events are disabled in channel channel0
 root@ubuntu:~# lttng enable-event -a -u --loglevel TRACE_CRIT
 All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
 root@ubuntu:~# lttng disable-event -a -u
 (infinite loop here...)
 -
 I guess it's probably due to the setting of loglevel through enable-event 
 twice..?
 Avi
 
 
 This body part will be downloaded on demand.

___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


Re: [lttng-dev] infinite loop invoked using lttng enable/disable-event

2013-06-25 Thread Thibault, Daniel
-Message d'origine-
Date: Tue, 25 Jun 2013 09:49:36 +0300
From: Avi Goren a...@reduxio.com

I'm using lttng 2.2.0 and encountered an infinite loop:
-
# lttng create
Session auto-20130624-165047 created.
Traces will be written in /home/avig/lttng-traces/auto-20130624-165047
# lttng enable-event -a -u --loglevel TRACE_ALERT
All UST events are enabled in channel channel0 for loglevel TRACE_ALERT
# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
# lttng disable-event -a -u
All UST events are disabled in channel channel0
# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
# lttng disable-event -a -u
(infinite loop here...)
-
I guess it's probably due to the setting of loglevel through enable-event 
twice..?
Avi
--

   I've reproduced it with one less step:

# lttng create loop
Session loop-20130624-165047 created.
Traces will be written in /home/avig/lttng-traces/loop-20130624-165047
# lttng enable-event -a -u --loglevel TRACE_ALERT
All UST events are enabled in channel channel0 for loglevel TRACE_ALERT
# lttng disable-event -a -u
All UST events are disabled in channel channel0
# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
# lttng list loop
(...)
Events:
  * (loglevel: TRACE_CRIT (2)) (type: tracepoint) [enabled]
  * (loglevel: TRACE_ALERT (1)) (type: tracepoint) [disabled]
# lttng disable-event -a -u
(LTTng hangs here)

   Remarkably, the session daemon remains very busy after the sudo kill command 
is sent, even though the trace has not even been started!  It refuses to die 
and I had to restart the system.  I'll post the bug up (with the session daemon 
log) shortly.

Daniel U. Thibault
Protection des systèmes et contremesures (PSC) | Systems Protection  
Countermeasures (SPC)
Cyber sécurité pour les missions essentielles (CME) | Mission Critical Cyber 
Security (MCCS)
R  D pour la défense Canada - Valcartier (RDDC Valcartier) | Defence RD 
Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Québec QC  G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ http://www.travelgis.com/map.asp?addr=918V%20QSDJ
Gouvernement du Canada | Government of Canada
http://www.valcartier.drdc-rddc.gc.ca/

___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev