/proc/<pid>/maps syntax

From: Boehm, Hans (hans.boehm_at_hp.com)
Date: 07/27/05

  • Next message: Eric W. Biederman: "Re: [PATCH 0/23] reboot-fixes"
    Date:	Wed, 27 Jul 2005 11:48:33 -0700
    To: <gc@linux.hpl.hp.com>
    
    

    FYI -

    [I'm not subscribed the kernel list.]

    The syntax for /proc/<pid>/maps as exported by
    the Linux kernel changed around August 2003.
    The layout of individual lines used to start
    with a bunch of fixed width fields (mostly addresses).
    It no longer does on 64-bit platforms. This
    introduced subtle breakage in our garbage collector.
    I'll post a patch shortly, though it seems to cause
    problems mostly in nonstandard configurations.

    I copied the kernel list, since I'd like to

    a) Encourage better documentation of such formats
    (as if I didn't have that problem).

    b) Possibly encourage consideration of other alternatives
    in future issues along these lines.

    Presumably this was done, so that 32-bit apps could
    decode /proc/self/maps?

    The down side is that

    a) It broke some existing 64-bit code.

    b) We ended up with an inferior format in the long run.
    Both the fixed-field width format, and a hypothetical
    alternative with no leading zeroes, have advantages in
    speeding up parsing. The latter is shorter, and probably
    easier to generate. The current hybrid seems to lose
    both benefits.

    Perhaps the documentation should clearly state that
    address and offset fields may or may not have leading zeroes,
    and declare the intent to eventually remove the remaining
    leading zeroes? I think that would have no impact on a sane
    parser that wasn't already broken by the last change?

    Hans
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Eric W. Biederman: "Re: [PATCH 0/23] reboot-fixes"

    Relevant Pages

    • Re: Quick selection of paragraph formats in Microsoft Word
      ... For real time documentations where format is important (e.g., ... because they allow the paragraph formats to be mapped into function keys ... through to make sure I am fully satisfied with my documentation and typing ...
      (microsoft.public.word.docmanagement)
    • Re: Quick selection of paragraph formats in Microsoft Word
      ... Go to Tools> Customize> Keyboard. ... For real time documentations where format is important (e.g., ... through to make sure I am fully satisfied with my documentation and typing ...
      (microsoft.public.word.docmanagement)
    • Re: Read text file to Temp file and apply formating and color chan
      ... As I said in my post, your sample code should auto-generate some relevant data. ... My best suggestion is that when a specific property or method in a class is mentioned to you, your first step is to review the MSDN documentation for that property or method. ... On that page, there is this comment: "For the RTF codes, see "rich text format Specification, version 1.6" in the MSDN library". ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: Read text file to Temp file and apply formating and color chan
      ... relevant data, as I am unsure how to do that being new to C#. ... Your data appears to have a fairly regular format. ... your first step is to review the MSDN documentation ... version 1.6" in the MSDN library". ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: Help!
      ... Man pages are one form of documentation. ... There is a strict format for man pages. ... and writing a format standard compliant ... Of course some commands (like bash) are really not ...
      (Debian-User)