-----Message d'origine-----
Envoyé : 30 juillet 2013 09:26
> If we use the command line interface you described, like
> lttng enable-event --processname a.out
> Then we will need a mechanism to distinguish processes with the same name.
> For example, I want to instrument my program for debugging but not touch any
> processes in production.
That's an odd use case you're describing. If one wanted to trace specific
process instances, one would naturally use PIDs instead of process names.
(Maybe the PID command option could accept enumerations of PIDs, i.e. something
like 'lttng whatever --pid={123, 456, 789}') If one did not know the PIDs in
advance (hence the reliance on process names), then the solution would be to
use filters on the events, no? Your to-be-debugged program could be run with
an environment (or internal global variable) setting that the filters could
check, for instance.
In the near future, one could use namespaces to isolate the production
instances from the experimental ones.
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/>
_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
