All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Tushar Shinde <mtk.tushar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org,
	myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	drepper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: For review: mtrace(1) man page
Date: Tue, 22 Jul 2014 10:17:43 +0200	[thread overview]
Message-ID: <53CE1E27.5020400@redhat.com> (raw)
In-Reply-To: <CABQpAL4JoZw8VqPNTuxnF2Nk+-zrt8srkzmxtYgi0XK9tC+9cQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Tushar,

On 07/22/2014 09:45 AM, Tushar Shinde wrote:
> Hi Jan,
>
> Is  this MTRACEDATA is same as environment  variable  MALLOC_TRACE 
> of MTRACE(3) ?
> If yes we should keep MALLOC_TRACE instead of MTRACEDATA to avoid 
> confusion.
>
> Tushar

thank you for noticing. Those are script arguments, not environment 
variables. Changed bold into underline.

.\" Copyright (c) 2013, Peter Schiffer (pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org)
.\"
.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2 of
.\" the License, or (at your option) any later version.
.\"
.\" The GNU General Public License's references to "object code"
.\" and "executables" are to be interpreted as the output of any
.\" document formatting or typesetting system, including
.\" intermediate and printed output.
.\"
.\" This manual is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
.\" License along with this manual; if not, see
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.TH MTRACE 1 2013-04-10 "GNU glibc 2.18" "Memory diagnostic tools"
.SH NAME
mtrace \- interpret the malloc trace log
.SH SYNOPSIS
.BR mtrace " [\fIOPTION\fR]... [\fIBINARY\fR] \fIMTRACEDATA\fR"
.SH DESCRIPTION
.B mtrace
is a Perl script used to interpret and provide human readable output
of the trace log created by
.BR mtrace (3)
function stored in the
\fIMTRACEDATA\fR
file.
If
\fIBINARY\fR
is provided, output of
.B mtrace
also contains source file name with line number information
of problem location
(assuming that
\fIBINARY\fR
was compiled with debugging information).

For more information about
.BR mtrace (3)
function and
.B mtrace
script usage, refer to the
.BR mtrace (3)
manual page.
.SH OPTIONS
.TP
.BI \fB\-\-help
Print help and exit.
.TP
.BI \fB\-\-version
Print version information and exit.
.SH BUGS
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
.SH SEE ALSO
.BR mtrace (3)
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-07-22  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  9:01 For review: mtrace(1) man page Jan Chaloupka
     [not found] ` <CABQpAL4JoZw8VqPNTuxnF2Nk+-zrt8srkzmxtYgi0XK9tC+9cQ@mail.gmail.com>
     [not found]   ` <CABQpAL4JoZw8VqPNTuxnF2Nk+-zrt8srkzmxtYgi0XK9tC+9cQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-22  8:17     ` Jan Chaloupka [this message]
     [not found]       ` <53CE1E27.5020400-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-30 13:34         ` Michael Kerrisk (man-pages)
     [not found] ` <53C8E24E.3040704-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-02 16:57   ` Mike Frysinger
2014-08-04  5:24     ` Jan Chaloupka
2014-08-22 23:07     ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CE1E27.5020400@redhat.com \
    --to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=drepper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=mtk.tushar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.