From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] Dead code in lttng.c
Date: Fri, 31 May 2013 14:34:34 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD12D2247A@VAL-E-02.valcartier.drdc-rddc.gc.ca> (raw)
In lttng-tools/src/bin/lttng/lttng.c, the check_args_no_sessiond function checks the command-line arguments for "specific options and commands that must not trigger a session daemon". The function detects the options "-h", "--h" (for "--help"), "--list-options", and "--list-commands", and the commands "version" and "view".
The parse_args function, on the other hand, detects "-V", "-h", "--list-commands", "--list-options" at its outset and *does not* reach the session daemon spawning check ( if (opt_no_sessiond == 0 && check_args_no_sessiond(argc, argv) == 0 && (check_sessiond() < 0)) ) in those cases.
So, why is check_args_no_sessiond checking for options at all? Considering the control flow of parse_args, check_args_no_sessiond should check *only* for the "version" and "view" commands.
If check_args_no_sessiond is to check the command-line options anyway (for completeness's sake, say), then it should check for the "-V"/"--version" option as well. And if the check for "--h" is satisfactory, the check for "--list-commands" and "--list-options" should be collapsed into a simple check for "--l".
(These observations are based on the May 23 commit, so my apologies if these points have already been addressed)
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 R&D 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/>
reply other threads:[~2013-05-31 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48CF5AC71E61DB46B70D0F388054EFFD12D2247A@VAL-E-02.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox