From mint-bounce@lists.fishpool.fi  Mon Sep 12 02:53:05 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] /kern documentation
From: Evan Langlois <Evan@CoolRunningConcepts.com>
To: Ingo Schmidt <ich@der-ingo.de>
Cc: MiNT-Liste <mint@fishpool.com>
In-Reply-To: <102530818.20050912013755@der-ingo.de>
References: <102530818.20050912013755@der-ingo.de>
Content-Type: text/plain
Date: Sun, 11 Sep 2005 19:50:36 -0500
Message-Id: <1126486236.29983.7.camel@taro.coolrunningconcepts.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc14.midphase.com
X-AntiAbuse: Original Domain - fishpool.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - CoolRunningConcepts.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: Evan@CoolRunningConcepts.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=0.7 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00, RCVD_IN_SORBS
X-Spam-Level: 

On Mon, 2005-09-12 at 01:37 +0200, Ingo Schmidt wrote:

> I am not a good C coder, but to me it seems, that in the format
> string, 13 arguments are present, while only 12 get passed in the end.

You are correct.  I'm also wondering if the %08x arguments should rather
be %08lx?   

> Does this maybe cause the weird behaviour? Or is everything correct
> and I am missing something?

Missing an argument could cause the issue or if the function is
expecting 16 bit integer arguments (%x and -mshort) and you give it 32
bit (ulong).  Depending on how the compiler passes arguments.

> What is the use of meminfo anyway? Which programs are using this? Or
> is it meant to be read by humans, just to have something nice to look
> at?  ;-)

I'm guessing its for applications like ps and top.

-- Evan


