From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] fread.3: Add example
Date: Fri, 19 Jun 2020 14:39:52 +0200 [thread overview]
Message-ID: <1ffd0ea3-824b-26e8-99bc-0b9b85c537e0@gmail.com> (raw)
In-Reply-To: <20200618142232.31022-1-arkadiusz@drabczyk.org>
Hello Arkadiusz,
On 6/18/20 4:22 PM, Arkadiusz Drabczyk wrote:
> Signed-off-by: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
Thanks! Patch applied. One glitch below edited.
> ---
> man3/fread.3 | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/man3/fread.3 b/man3/fread.3
> index 2dd7be9..4af3850 100644
> --- a/man3/fread.3
> +++ b/man3/fread.3
> @@ -113,6 +113,61 @@ T} Thread safety MT-Safe
> .TE
> .SH CONFORMING TO
> POSIX.1-2001, POSIX.1-2008, C89.
> +.SH EXAMPLES
> +The program below demonstrates the use of
> +.BR fread ()
> +by parsing /bin/sh ELF executable in binary mode and printing its
> +magic and class:
> +.PP
> +.in +4n
> +.EX
> +$ \fB./a.out\fP
> +./a.out
I removed the preceding line (which did not render, and I assume was
cruft you meant to delete).
Thanks,
Michael
> +ELF magic: 0x7f454c46
> +Class: 0x02
> +.EE
> +.in
> +.SS Program source
> +\&
> +.EX
> +#include <stdio.h>
> +#include <stdlib.h>
> +
> +int
> +main(void)
> +{
> + FILE *fp = fopen("/bin/sh", "rb");
> + if (!fp) {
> + perror("fopen");
> + return EXIT_FAILURE;
> + }
> +
> + unsigned char buffer[4];
> +
> + size_t ret =
> + fread(buffer, sizeof(buffer) / sizeof(*buffer), sizeof(*buffer),
> + fp);
> + if (ret != sizeof(*buffer)) {
> + fprintf(stderr, "fread() failed: %zu\en", ret);
> + exit(EXIT_FAILURE);
> + }
> +
> + printf("ELF magic: %#04x%02x%02x%02x\en", buffer[0], buffer[1],
> + buffer[2], buffer[3]);
> +
> + ret = fread(buffer, 1, 1, fp);
> + if (ret != 1) {
> + fprintf(stderr, "fread() failed: %zu\en", ret);
> + exit(EXIT_FAILURE);
> + }
> +
> + printf("Class: %#04x\en", buffer[0]);
> +
> + fclose(fp);
> +
> + exit(EXIT_SUCCESS);
> +}
> +.EE
> .SH SEE ALSO
> .BR read (2),
> .BR write (2),
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-06-19 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:22 [PATCH v2] fread.3: Add example Arkadiusz Drabczyk
2020-06-19 12:39 ` Michael Kerrisk (man-pages) [this message]
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=1ffd0ea3-824b-26e8-99bc-0b9b85c537e0@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=arkadiusz@drabczyk.org \
--cc=linux-man@vger.kernel.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).