From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: 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: memusage(1) man page
Date: Tue, 22 Jul 2014 10:07:32 +0200 [thread overview]
Message-ID: <53CE1BC4.6040707@redhat.com> (raw)
In-Reply-To: <53CE0517.2040005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Adding example with small C code to demonstrate progress of memory usage
.\" 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 MEMUSAGESTAT 1 2013-04-10 "GNU glibc 2.18" "Memory diagnostic tools"
.SH NAME
memusagestat \- generate graphic from memory profiling data
.SH SYNOPSIS
.BR memusagestat " [\fIOPTION\fR]... \fIDATAFILE\fR [\fIOUTFILE\fR]"
.SH DESCRIPTION
.B memusagestat
can create a PNG file with graphical representation of memory profiling
data.
Red line in the graph shows the heap usage (allocated memory),
green line shows the stack usage,
x-scale number of memory handling functions calls or time (\fB-t\fR option).
.I DATAFILE
is a binary data file generated by
.BR memusage (1)
utility with
.B -d
option.
.SH OPTIONS
.TP
.BI \-o\ file \fR,\ \fB\-\-output= file
Name of the output file.
.TP
.BI \-s\ string \fR,\ \fB\-\-string= string
Title string used in the output graphic.
.TP
.BI \-t\fR,\ \fB\-\-time
Generate output linear to time
(default is linear to number of function calls).
.TP
.BI \-T\fR,\ \fB\-\-total
Also draw graph for total memory consumption.
.TP
.BI \-x\ size \fR,\ \fB\-\-x-size= size
Make graphic size pixels wide.
.TP
.BI \-y\ size \fR,\ \fB\-\-y\-size= size
Make graphic size pixels high.
.TP
.BI \-?\fR,\ \fB\-\-help
Print help and exit.
.TP
.BI \fB\-\-usage
Print a short usage message and exit.
.TP
.BI \-V\fR,\ \fB\-\-version
Print version information and exit.
.SH EXAMPLES
Here is a simple program \fImemusagestatexample.c\fR simulating increase
and decrease of memory usage:
.RS 4
#include <stdio.h>
.RS 0
#include <stdlib.h>
.RE
.RS 0
#define CYCLES 20
.RE
int main(int argc, char ** argv) {
int i, j;
int *p = NULL;
printf("malloc: %d\\n", sizeof(int)*100);
p = malloc(sizeof(int)*100);
for (i = 0; i < CYCLES; i++) {
if (i < CYCLES/2) j = i; else j--;
printf("realloc: %d\\n", sizeof(int)*((j)*50 + 110));
p = realloc(p, sizeof(int)*(j*50 + 100));
printf("realloc: %d\\n", sizeof(int)*((j+1)*150 + 110));
p = realloc(p, sizeof(int)*((j+1)*150 + 110));
}
free(p);
return 0;
.RS 0
}
.RE
.RE
After compiling and running the following, you can see progress of
memory usage (memusagestatexample.png):
memusage --data=memusagestatexample.dat ./memusagestatexample
.RS 0
memusagestat memusagestatexample.dat memusagestatexample.png
.RE
.SH BUGS
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
.SH SEE ALSO
.BR memusage (1)
--
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
next prev parent reply other threads:[~2014-07-22 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:00 For review: memusage(1) man page Jan Chaloupka
2014-07-18 9:20 ` Alfred M. Szmidt
2014-07-18 9:50 ` Jan Chaloupka
[not found] ` <E1X84Kh-00041J-2z-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-22 6:10 ` Michael Kerrisk (man-pages)
[not found] ` <53CE004A.3060706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-22 8:39 ` Alfred M. Szmidt
[not found] ` <E1X9VbA-0002Bk-Ox-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-22 10:20 ` Jan Chaloupka
[not found] ` <53CE3AF3.40005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 11:00 ` Alfred M. Szmidt
[not found] ` <E1X9XoF-0007Vz-Lm-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-24 5:25 ` Jan Chaloupka
2014-07-24 7:26 ` Alfred M. Szmidt
[not found] ` <E1XADPx-0007U6-2t-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-24 7:39 ` Jan Chaloupka
2014-07-22 19:02 ` Michael Kerrisk (man-pages)
2014-07-23 14:41 ` Alfred M. Szmidt
[not found] ` <53C8E244.2080901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 6:14 ` Michael Kerrisk (man-pages)
[not found] ` <53CE0144.7050405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-22 6:30 ` Jan Chaloupka
[not found] ` <53CE0517.2040005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 8:07 ` Jan Chaloupka [this message]
[not found] ` <53CE1BC4.6040707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-04 5:26 ` Jan Chaloupka
2014-08-30 13:57 ` Michael Kerrisk (man-pages)
[not found] ` <5401D83C.3050806-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-01 7:22 ` Jan Chaloupka
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=53CE1BC4.6040707@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).