> -g _圆4_sys_execve -O nofuncgraph-irqs \ > Document the expected behaviour ftrace users should see depending on > realises that everything is working as expected but documenting it could > Some time after one digs into trace-cmd's and libc's code base, one > something wrong in any of the parts involved in the tracing operation. > cryptic for untrained eyes and makes one wonder whether there is > While the routine works as expected, its behaviour can seem a bit > attempts that execvp() routine had done until it could find the > _圆4_sys_execve() syscall where will be equal to the number of > of the PATH env var then you should see invocations of the > If you run a command which is meant to be found in one of the entries > is launched via the libc's execvp() routine. > In tracecmd/trace-record.c:, trace-cmd record -F To: Paulo Miguel Almeida Cc: linux-trace-devel 2:09 ` Paulo Miguel Almeida 0 siblings, 1 reply 9 messages in threadįrom: Steven Rostedt 23:13 UTC ( / raw) 22:52 trace-cmd: document expected behaviour of execvp for record command Paulo Miguel 23:13 ` Steven Rostedt * Re: trace-cmd: document expected behaviour of execvp for record command ^ raw reply related 9 messages in thread Similar to *-F* but lets you specify a process ID to trace. directory pathnames specified in the PATH environment variable. will invoke execve() syscall for every entry in the colon-separated list of Note: if the specified filename is neither absolute or relative then libc Using *-F* will let you trace only events that are caused by the given a/Documentation/trace-cmd/trace-cmd-record.1.txt Realises that everything is working as expected but documenting it couldĭocument the expected behaviour ftrace users should see depending on Some time after one digs into trace-cmd's and libc's code base, one Something wrong in any of the parts involved in the tracing operation. While the routine works as expected, its behaviour can seem a bitĬryptic for untrained eyes and makes one wonder whether there is _圆4_sys_execve() syscall where will be equal to the number ofĪttempts that execvp() routine had done until it could find the Of the PATH env var then you should see invocations of the If you run a command which is meant to be found in one of the entries Is launched via the libc's execvp() routine. In tracecmd/trace-record.c:, trace-cmd record -F 23:13 ` Steven Rostedt 0 siblings, 1 reply 9 messages in threadįrom: Paulo Miguel Almeida 22:52 UTC ( / raw) Trace-cmd: document expected behaviour of execvp for record command All of help / color / mirror / Atom feed * trace-cmd: document expected behaviour of execvp for record command 22:52 Paulo Miguel Almeida
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |