[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

address@hidden: Bug#186448: time: time's memory usage tracking is broke

From: Dirk Eddelbuettel
Subject: address@hidden: Bug#186448: time: time's memory usage tracking is broken]
Date: Sat, 12 Apr 2003 16:50:48 -0500
User-agent: Mutt/1.3.28i


I'm Debian's maintainer for GNU time, and received the following bug report.
As time has been de facto without an upstream maintainer for years, I am
taking the liberty of forwarding the report to this list in the hope that
either someone may come forward to work on this, or better still, someone
already is and he may tell me :). 

A little bit on an ensuing email exchange between Peter and myself is in the
Debian bug archive at the address http://bugs.debian.org/186448
Regards,  Dirk   

----- Forwarded message from Peter Eckersley <address@hidden> -----

Envelope-to: address@hidden
Delivery-date: Thu, 27 Mar 2003 00:38:58 -0600
Subject: Bug#186448: time: time's memory usage tracking is broken
Reply-To: Peter Eckersley <address@hidden>, address@hidden
From: Peter Eckersley <address@hidden>
To: address@hidden

Package: time
Version: 1.7-15
Severity: normal

Some of time's documented memory tracking features don't appear to work:

address@hidden:~$ /usr/bin/time -f "%M mem, %K avg, %F/%R pfs" vim 

0 mem, 0 avg, 1039/23403 pfs

Is this possibly kernel-related?  The relevant data structure is in
/usr/include/linux/resource.h, which indicates that some parts of struct rusage
don't exist yet (in which case, should these flags be taken out of the man

-- System Information
Debian Release: 3.0
Kernel Version: Linux luminance.reworld.org 2.4.17 #1 Tue Feb 12 13:29:22 EST 
2002 i686 unknown

Versions of the packages time depends on:
ii  libc6          2.3.1-13       GNU C Library: Shared libraries and Timezone

----- End forwarded message -----

Wishful thinking can dominate much of the work of a profession for a decade,
but not indefinitely.   -- Robert Shiller, on Efficient Markets models, 2002

reply via email to

[Prev in Thread] Current Thread [Next in Thread]