2019-02-22 23:25:01 +01:00
|
|
|
#include "cache.h"
|
|
|
|
#include "config.h"
|
|
|
|
#include "run-command.h"
|
|
|
|
#include "quote.h"
|
|
|
|
#include "version.h"
|
|
|
|
#include "trace2/tr2_dst.h"
|
2019-04-15 22:39:47 +02:00
|
|
|
#include "trace2/tr2_sysenv.h"
|
2019-02-22 23:25:01 +01:00
|
|
|
#include "trace2/tr2_tbuf.h"
|
|
|
|
#include "trace2/tr2_tgt.h"
|
|
|
|
#include "trace2/tr2_tls.h"
|
|
|
|
|
2019-10-05 00:08:21 +02:00
|
|
|
static struct tr2_dst tr2dst_normal = { TR2_SYSENV_NORMAL, 0, 0, 0, 0 };
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
/*
|
2019-04-15 22:39:47 +02:00
|
|
|
* Use the TR2_SYSENV_NORMAL_BRIEF setting to omit the "<time> <file>:<line>"
|
2019-02-22 23:25:01 +01:00
|
|
|
* fields from each line written to the builtin normal target.
|
|
|
|
*
|
|
|
|
* Unit tests may want to use this to help with testing.
|
|
|
|
*/
|
2019-04-15 22:39:47 +02:00
|
|
|
static int tr2env_normal_be_brief;
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
#define TR2FMT_NORMAL_FL_WIDTH (50)
|
|
|
|
|
|
|
|
static int fn_init(void)
|
|
|
|
{
|
|
|
|
int want = tr2_dst_trace_want(&tr2dst_normal);
|
|
|
|
int want_brief;
|
2019-04-15 22:39:47 +02:00
|
|
|
const char *brief;
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
if (!want)
|
|
|
|
return want;
|
|
|
|
|
2019-04-15 22:39:47 +02:00
|
|
|
brief = tr2_sysenv_get(TR2_SYSENV_NORMAL_BRIEF);
|
2019-02-22 23:25:01 +01:00
|
|
|
if (brief && *brief &&
|
|
|
|
((want_brief = git_parse_maybe_bool(brief)) != -1))
|
2019-04-15 22:39:47 +02:00
|
|
|
tr2env_normal_be_brief = want_brief;
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
return want;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_term(void)
|
|
|
|
{
|
|
|
|
tr2_dst_trace_disable(&tr2dst_normal);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void normal_fmt_prepare(const char *file, int line, struct strbuf *buf)
|
|
|
|
{
|
|
|
|
strbuf_setlen(buf, 0);
|
|
|
|
|
2019-04-15 22:39:47 +02:00
|
|
|
if (!tr2env_normal_be_brief) {
|
2019-02-22 23:25:01 +01:00
|
|
|
struct tr2_tbuf tb_now;
|
|
|
|
|
|
|
|
tr2_tbuf_local_time(&tb_now);
|
|
|
|
strbuf_addstr(buf, tb_now.buf);
|
|
|
|
strbuf_addch(buf, ' ');
|
|
|
|
|
|
|
|
if (file && *file)
|
|
|
|
strbuf_addf(buf, "%s:%d ", file, line);
|
|
|
|
while (buf->len < TR2FMT_NORMAL_FL_WIDTH)
|
|
|
|
strbuf_addch(buf, ' ');
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void normal_io_write_fl(const char *file, int line,
|
|
|
|
const struct strbuf *buf_payload)
|
|
|
|
{
|
|
|
|
struct strbuf buf_line = STRBUF_INIT;
|
|
|
|
|
|
|
|
normal_fmt_prepare(file, line, &buf_line);
|
|
|
|
strbuf_addbuf(&buf_line, buf_payload);
|
|
|
|
tr2_dst_write_line(&tr2dst_normal, &buf_line);
|
|
|
|
strbuf_release(&buf_line);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_version_fl(const char *file, int line)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "version %s", git_version_string);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
2019-04-15 22:39:44 +02:00
|
|
|
static void fn_start_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute, const char **argv)
|
2019-02-22 23:25:01 +01:00
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addstr(&buf_payload, "start ");
|
2019-08-09 17:00:56 +02:00
|
|
|
sq_append_quote_argv_pretty(&buf_payload, argv);
|
2019-02-22 23:25:01 +01:00
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_exit_fl(const char *file, int line, uint64_t us_elapsed_absolute,
|
|
|
|
int code)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
double elapsed = (double)us_elapsed_absolute / 1000000.0;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "exit elapsed:%.6f code:%d", elapsed, code);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_signal(uint64_t us_elapsed_absolute, int signo)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
double elapsed = (double)us_elapsed_absolute / 1000000.0;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "signal elapsed:%.6f code:%d", elapsed,
|
|
|
|
signo);
|
|
|
|
normal_io_write_fl(__FILE__, __LINE__, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_atexit(uint64_t us_elapsed_absolute, int code)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
double elapsed = (double)us_elapsed_absolute / 1000000.0;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "atexit elapsed:%.6f code:%d", elapsed, code);
|
|
|
|
normal_io_write_fl(__FILE__, __LINE__, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void maybe_append_string_va(struct strbuf *buf, const char *fmt,
|
|
|
|
va_list ap)
|
|
|
|
{
|
2019-03-19 18:13:46 +01:00
|
|
|
if (fmt && *fmt) {
|
2019-02-22 23:25:01 +01:00
|
|
|
va_list copy_ap;
|
|
|
|
|
|
|
|
va_copy(copy_ap, ap);
|
|
|
|
strbuf_vaddf(buf, fmt, copy_ap);
|
|
|
|
va_end(copy_ap);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_error_va_fl(const char *file, int line, const char *fmt,
|
|
|
|
va_list ap)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
2019-08-08 16:19:02 +02:00
|
|
|
strbuf_addstr(&buf_payload, "error");
|
|
|
|
if (fmt && *fmt) {
|
|
|
|
strbuf_addch(&buf_payload, ' ');
|
|
|
|
maybe_append_string_va(&buf_payload, fmt, ap);
|
|
|
|
}
|
2019-02-22 23:25:01 +01:00
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_command_path_fl(const char *file, int line, const char *pathname)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "cmd_path %s", pathname);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
tr2: log parent process name
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>
2021-07-22 03:27:07 +02:00
|
|
|
static void fn_command_ancestry_fl(const char *file, int line, const char **parent_names)
|
|
|
|
{
|
|
|
|
const char *parent_name = NULL;
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
/* cmd_ancestry parent <- grandparent <- great-grandparent */
|
|
|
|
strbuf_addstr(&buf_payload, "cmd_ancestry ");
|
|
|
|
while ((parent_name = *parent_names++)) {
|
|
|
|
strbuf_addstr(&buf_payload, parent_name);
|
|
|
|
/* if we'll write another one after this, add a delimiter */
|
|
|
|
if (parent_names && *parent_names)
|
|
|
|
strbuf_addstr(&buf_payload, " <- ");
|
|
|
|
}
|
|
|
|
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
2019-02-22 23:25:01 +01:00
|
|
|
static void fn_command_name_fl(const char *file, int line, const char *name,
|
|
|
|
const char *hierarchy)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "cmd_name %s", name);
|
|
|
|
if (hierarchy && *hierarchy)
|
|
|
|
strbuf_addf(&buf_payload, " (%s)", hierarchy);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_command_mode_fl(const char *file, int line, const char *mode)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "cmd_mode %s", mode);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_alias_fl(const char *file, int line, const char *alias,
|
|
|
|
const char **argv)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addf(&buf_payload, "alias %s -> ", alias);
|
|
|
|
sq_append_quote_argv_pretty(&buf_payload, argv);
|
2019-02-22 23:25:01 +01:00
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_child_start_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute,
|
|
|
|
const struct child_process *cmd)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addf(&buf_payload, "child_start[%d]", cmd->trace2_child_id);
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
if (cmd->dir) {
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addstr(&buf_payload, " cd ");
|
2019-02-22 23:25:01 +01:00
|
|
|
sq_quote_buf_pretty(&buf_payload, cmd->dir);
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addstr(&buf_payload, ";");
|
2019-02-22 23:25:01 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* TODO if (cmd->env) { Consider dumping changes to environment. }
|
|
|
|
* See trace_add_env() in run-command.c as used by original trace.c
|
|
|
|
*/
|
|
|
|
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addch(&buf_payload, ' ');
|
2019-02-22 23:25:01 +01:00
|
|
|
if (cmd->git_cmd)
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addstr(&buf_payload, "git ");
|
run-command API: remove "argv" member, always use "args"
Remove the "argv" member from the run-command API, ever since "args"
was added in c460c0ecdca (run-command: store an optional argv_array,
2014-05-15) being able to provide either "argv" or "args" has led to
some confusion and bugs.
If we hadn't gone in that direction and only had an "argv" our
problems wouldn't have been solved either, as noted in [1] (and in the
documentation amended here) it comes with inherent memory management
issues: The caller would have to hang on to the "argv" until the
run-command API was finished. If the "argv" was an argument to main()
this wasn't an issue, but if it it was manually constructed using the
API might be painful.
We also have a recent report[2] of a user of the API segfaulting,
which is a direct result of it being complex to use. This commit
addresses the root cause of that bug.
This change is larger than I'd like, but there's no easy way to avoid
it that wouldn't involve even more verbose intermediate steps. We use
the "argv" as the source of truth over the "args", so we need to
change all parts of run-command.[ch] itself, as well as the trace2
logging at the same time.
The resulting Windows-specific code in start_command() is a bit nasty,
as we're now assigning to a strvec's "v" member, instead of to our own
"argv". There was a suggestion of some alternate approaches in reply
to an earlier version of this commit[3], but let's leave larger a
larger and needless refactoring of this code for now.
1. http://lore.kernel.org/git/YT6BnnXeAWn8BycF@coredump.intra.peff.net
2. https://lore.kernel.org/git/20211120194048.12125-1-ematsumiya@suse.de/
3. https://lore.kernel.org/git/patch-5.5-ea1011f7473-20211122T153605Z-avarab@gmail.com/
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-11-25 23:52:22 +01:00
|
|
|
sq_append_quote_argv_pretty(&buf_payload, cmd->args.v);
|
2019-02-22 23:25:01 +01:00
|
|
|
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_child_exit_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute, int cid, int pid,
|
|
|
|
int code, uint64_t us_elapsed_child)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
double elapsed = (double)us_elapsed_child / 1000000.0;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "child_exit[%d] pid:%d code:%d elapsed:%.6f",
|
|
|
|
cid, pid, code, elapsed);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
2021-09-20 17:36:12 +02:00
|
|
|
static void fn_child_ready_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute, int cid, int pid,
|
|
|
|
const char *ready, uint64_t us_elapsed_child)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
double elapsed = (double)us_elapsed_child / 1000000.0;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "child_ready[%d] pid:%d ready:%s elapsed:%.6f",
|
|
|
|
cid, pid, ready, elapsed);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
2019-02-22 23:25:01 +01:00
|
|
|
static void fn_exec_fl(const char *file, int line, uint64_t us_elapsed_absolute,
|
|
|
|
int exec_id, const char *exe, const char **argv)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "exec[%d] ", exec_id);
|
2019-08-09 17:00:56 +02:00
|
|
|
if (exe) {
|
2019-02-22 23:25:01 +01:00
|
|
|
strbuf_addstr(&buf_payload, exe);
|
2019-08-09 17:00:56 +02:00
|
|
|
strbuf_addch(&buf_payload, ' ');
|
|
|
|
}
|
|
|
|
sq_append_quote_argv_pretty(&buf_payload, argv);
|
2019-02-22 23:25:01 +01:00
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_exec_result_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute, int exec_id,
|
|
|
|
int code)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "exec_result[%d] code:%d", exec_id, code);
|
|
|
|
if (code > 0)
|
|
|
|
strbuf_addf(&buf_payload, " err:%s", strerror(code));
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_param_fl(const char *file, int line, const char *param,
|
|
|
|
const char *value)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addf(&buf_payload, "def_param %s=%s", param, value);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_repo_fl(const char *file, int line,
|
|
|
|
const struct repository *repo)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
strbuf_addstr(&buf_payload, "worktree ");
|
|
|
|
sq_quote_buf_pretty(&buf_payload, repo->worktree);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void fn_printf_va_fl(const char *file, int line,
|
|
|
|
uint64_t us_elapsed_absolute, const char *fmt,
|
|
|
|
va_list ap)
|
|
|
|
{
|
|
|
|
struct strbuf buf_payload = STRBUF_INIT;
|
|
|
|
|
|
|
|
maybe_append_string_va(&buf_payload, fmt, ap);
|
|
|
|
normal_io_write_fl(file, line, &buf_payload);
|
|
|
|
strbuf_release(&buf_payload);
|
|
|
|
}
|
|
|
|
|
|
|
|
struct tr2_tgt tr2_tgt_normal = {
|
|
|
|
&tr2dst_normal,
|
|
|
|
|
|
|
|
fn_init,
|
|
|
|
fn_term,
|
|
|
|
|
|
|
|
fn_version_fl,
|
|
|
|
fn_start_fl,
|
|
|
|
fn_exit_fl,
|
|
|
|
fn_signal,
|
|
|
|
fn_atexit,
|
|
|
|
fn_error_va_fl,
|
|
|
|
fn_command_path_fl,
|
tr2: log parent process name
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>
2021-07-22 03:27:07 +02:00
|
|
|
fn_command_ancestry_fl,
|
2019-02-22 23:25:01 +01:00
|
|
|
fn_command_name_fl,
|
|
|
|
fn_command_mode_fl,
|
|
|
|
fn_alias_fl,
|
|
|
|
fn_child_start_fl,
|
|
|
|
fn_child_exit_fl,
|
2021-09-20 17:36:12 +02:00
|
|
|
fn_child_ready_fl,
|
2019-02-22 23:25:01 +01:00
|
|
|
NULL, /* thread_start */
|
|
|
|
NULL, /* thread_exit */
|
|
|
|
fn_exec_fl,
|
|
|
|
fn_exec_result_fl,
|
|
|
|
fn_param_fl,
|
|
|
|
fn_repo_fl,
|
|
|
|
NULL, /* region_enter */
|
|
|
|
NULL, /* region_leave */
|
|
|
|
NULL, /* data */
|
|
|
|
NULL, /* data_json */
|
|
|
|
fn_printf_va_fl,
|
|
|
|
};
|