Re: [PATCH v2 1/2] mtrace: record backtrace of memory allocation/deallocation

[Joseph Myers <joseph at codesourcery dot com>]

On Tue, 20 Nov 2018, Kyeong Yoo wrote:

> +To generate more detailed backtrace information of function calls to
> +@code{malloc} etc, set an environment variable named @code{MALLOC_TRACE_LEVEL}
> +with a number between 1 and 15. This indicates the maximum number of
> +function pointers to generate in the backtrace information.

@env for environment variables; two spaces after "." in Texinfo sources.

> +A list of pointers are printed with '#' mark before each memory

' is a right quote in Texinfo, so you need @samp{#} for proper quoting.

> +For cross-compilation, @code{mtrace} can generate meaningful output
> +with additional command line options @code{--prefix=PREFIX} and
> +@code{--addr2line=CMD} along with @code{/proc/<PID>maps} file copied
> +from the target device.

@option for command-line options, and @var for metasyntactic variables 
(lowercase inside @var, so @var{prefix} etc.).  @file for filenames.

I expect people will look at the patch in more detail once the copyright 
assignment is done.

https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future

-- 
Joseph S. Myers
joseph@codesourcery.com