From: Justin T Pryzby <justinp-sqUMWyTXAylY7ZOgVWywrQ@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Siddu <siddu.sjce-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: possibly a Bug in proc man page
Date: Tue, 5 Jan 2010 09:45:23 -0700 [thread overview]
Message-ID: <20100105164523.GA8277@norchemlab.com> (raw)
In-Reply-To: <cfd18e0f1001050831n37787505y2d05d37aca2cbaa4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Jan 06, 2010 at 05:31:53AM +1300, Michael Kerrisk wrote:
> Siddu,
>
> On Fri, Jan 1, 2010 at 10:42 PM, Siddu <siddu.sjce-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hello folks
> >
> >
> > The format in /proc/<pid>/maps seems to be updated. In the man page,
> > for every mapped library it lists only two section while in reality there
> > are three sections like shown below
>
> I don't understand what yo mean here. Can you please say more.
In his example, libc was listed three times, but in proc(5) libc is
listed only twice.
Justin
--
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
prev parent reply other threads:[~2010-01-05 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9b0a5b991001010142w12fe5259v5819b925d13f352c@mail.gmail.com>
[not found] ` <9b0a5b991001010142w12fe5259v5819b925d13f352c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-05 16:31 ` possibly a Bug in proc man page Michael Kerrisk
[not found] ` <cfd18e0f1001050831n37787505y2d05d37aca2cbaa4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-05 16:45 ` Justin T Pryzby [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=20100105164523.GA8277@norchemlab.com \
--to=justinp-squmwytxayly7zogvwywrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=siddu.sjce-Re5JQEeQqe8AvxtiuMwx3w@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.