Changes

Execution of the parasite code starts with the function

Execution of the parasite code starts with the function

int main(void *arg_p, unsigned int arg_s);

int main(void *arg_p, unsigned int arg_s);

that should be present in your code. The arg_p and arg_s is the binary argument that will get delivered to parasite code by complel _start() call (see below). Sometimes this binary argument can be treated as CLI arguments argc/argv.

that should be present in your code. The <code>arg_p</code> and <code>arg_s</code> is the binary argument that will get delivered to parasite code by complel <code>_start()</code> call (see below). Sometimes this binary argument can be treated as CLI arguments argc/argv.

=== Compile the sources and pack the binary ===

=== Compile the sources and pack the binary ===

Take a program on C and compile it with compel flags

Take a program on C and compile it with compel flags

$ gcc -c foo.c -o foo.o $(compel cflags) -I

$ gcc -c foo.c -o foo.o $(compel cflags) -I

To combine the foo.o out of many sources, they should all be linked with compel flags as well

To combine the foo.o out of many sources, they should all be linked with compel flags as well

$ ld foo_1.o foo_2.o -o foo.o $(compel ldflags)

$ ld foo_1.o foo_2.o -o foo.o $(compel ldflags)

 

</pre>

The compel-headers is devel/include/ after make install-devel.

Pack the binary. Packing would link the object file with compel plugins (see below)

Pack the binary. Packing would link the object file with compel plugins (see below)

$ compel pack foo.o -o foo.compel.o -L [-l]

$ compel pack foo.o -o foo.compel.o [-l plugin]

The compel-libs is devel/lib/compel/ after make install-devel.

The <code>-l</code> option specifies plugins to be added to the packed binary. Plugin <code>std</code> is added all the time w/o any options.

The foo.compel.o is ready for remote execution (foo.o was not).

The foo.compel.o is ready for remote execution (foo.o was not).

Using CLI like this

Using CLI like this

$ compel run -f foo.compel.o -p $pid

$ compel run -f foo.compel.o -p $pid [args]

Or, you can link with libcompel.so and use

Or, you can link with libcompel.so and use

libcompel_exec() libcompel_exec_start()/libcompel_exec_end()

libcompel_exec() libcompel_exec_start()/libcompel_exec_end()

calls described in include/compel/compel.h header. The test/ directory contains several examples of how to launch parasites.

calls.

The library calls require binary argument that will get copied into parasite context and passed to it via arg_p/arg_s pair. When run from CLI the arguments are packed in argc/argv manner.

The library calls require binary argument that will get copied into parasite context and passed to it via arg_p/arg_s pair. When run from CLI the arguments are packed in argc/argv manner.

If you run the parasite binary from CLI, the tail command line arguments are passed into the parasite main() function.

If you run the parasite binary from CLI, the tail command line arguments are passed into the parasite main() function.

$ compel run -f foo.compel.o -p 123 -- arg1 arg2 arg3

$ compel run -f foo.compel.o -p 123 -- arg1 arg2 arg3

In the main() common argc and argv are accessed using the

In the main() common argc and argv are accessed using the