mirror of
https://github.com/git/git
synced 2024-08-24 02:11:08 +00:00
2f732bf15e
It can be useful to tell who invoked Git - was it invoked manually by a user via CLI or script? By an IDE? In some cases - like 'repo' tool - we can influence the source code and set the GIT_TRACE2_PARENT_SID environment variable from the caller process. In 'repo''s case, that parent SID is manipulated to include the string "repo", which means we can positively identify when Git was invoked by 'repo' tool. However, identifying parents that way requires both that we know which tools invoke Git and that we have the ability to modify the source code of those tools. It cannot scale to keep up with the various IDEs and wrappers which use Git, most of which we don't know about. Learning which tools and wrappers invoke Git, and how, would give us insight to decide where to improve Git's usability and performance. Unfortunately, there's no cross-platform reliable way to gather the name of the parent process. If procfs is present, we can use that; otherwise we will need to discover the name another way. However, the process ID should be sufficient to look up the process name on most platforms, so that code may be shareable. Git for Windows gathers similar information and logs it as a "data_json" event. However, since "data_json" has a variable format, it is difficult to parse effectively in some languages; instead, let's pursue a dedicated "cmd_ancestry" event to record information about the ancestry of the current process and a consistent, parseable way. Git for Windows also gathers information about more than one generation of parent. In Linux further ancestry info can be gathered with procfs, but it's unwieldy to do so. In the interest of later moving Git for Windows ancestry logging to the 'cmd_ancestry' event, and in the interest of later adding more ancestry to the Linux implementation - or of adding this functionality to other platforms which have an easier time walking the process tree - let's make 'cmd_ancestry' accept an array of parentage. Signed-off-by: Emily Shaffer <emilyshaffer@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
55 lines
1.4 KiB
Perl
55 lines
1.4 KiB
Perl
#!/usr/bin/perl
|
|
#
|
|
# Scrub the variable fields from the normal trace2 output to
|
|
# make testing easier.
|
|
|
|
use strict;
|
|
use warnings;
|
|
|
|
my $float = '[0-9]*\.[0-9]+([eE][-+]?[0-9]+)?';
|
|
|
|
# This code assumes that the trace2 data was written with bare
|
|
# turned on (which omits the "<clock> <file>:<line>" prefix.
|
|
|
|
while (<>) {
|
|
# Various messages include an elapsed time in the middle
|
|
# of the message. Replace the time with a placeholder to
|
|
# simplify our HEREDOC in the test script.
|
|
s/elapsed:$float/elapsed:_TIME_/g;
|
|
|
|
my $line = $_;
|
|
|
|
# we expect:
|
|
# start <argv0> [<argv1> [<argv2> [...]]]
|
|
#
|
|
# where argv0 might be a relative or absolute path, with
|
|
# or without quotes, and platform dependent. Replace argv0
|
|
# with a token for HEREDOC matching in the test script.
|
|
|
|
if ($line =~ m/^start/) {
|
|
$line =~ /^start\s+(.*)/;
|
|
my $argv = $1;
|
|
$argv =~ m/(\'[^\']*\'|[^ ]+)\s+(.*)/;
|
|
my $argv_0 = $1;
|
|
my $argv_rest = $2;
|
|
|
|
print "start _EXE_ $argv_rest\n";
|
|
}
|
|
elsif ($line =~ m/^cmd_path/) {
|
|
# Likewise, the 'cmd_path' message breaks out argv[0].
|
|
#
|
|
# This line is only emitted when RUNTIME_PREFIX is defined,
|
|
# so just omit it for testing purposes.
|
|
# print "cmd_path _EXE_\n";
|
|
}
|
|
elsif ($line =~ m/^cmd_ancestry/) {
|
|
# 'cmd_ancestry' is not implemented everywhere, so for portability's
|
|
# sake, skip it when parsing normal.
|
|
#
|
|
# print "$line";
|
|
}
|
|
else {
|
|
print "$line";
|
|
}
|
|
}
|