Re: Optimized gcc 4.3.0 build on Windows returns 0 secs for all time values of system-process-attributes

[dhruva]

Hello,

On Fri, Jan 2, 2009 at 12:30 AM, Eli Zaretskii <address@hidden> wrote:
>> Date: Thu, 1 Jan 2009 19:13:05 +0530
>> From: dhruva <address@hidden>
>> Cc: "Juanma Barranquero" <address@hidden>, "Eli Zaretskii" <address@hidden>,
>>       address@hidden
>>
>> Here is a modified patch that seems to give me different values! Not
>> sure how to interpret it though :(
>
> Use Proced, it will display them in human-readable format.  Do the
> values it shows seem reasonable?

It does. But I notice process started in 2008 have the year and 00:00
in the start time. Maybe, it is a separate issue.
Ex:
  dhruva 1400  0.0  1.1  10:21 00:00 emacs.exe
  dhruva 2476  0.0  0.1  10:20 00:00 cmd.exe
  dhruva 2340  0.0  2.7  08:50 00:00 opera.exe
  dhruva 4252  0.0  1.4   2008 00:01 procexp.exe
  dhruva 2956  0.0  0.6   2008 00:00 BTSTAC~1.EXE
  dhruva 1912  0.0  0.2   2008 00:00 DLG.exe

> Anyway, I don't like fixing a problem we don't understand.  I'd like
> to find out what is wrong with the original code, before we start
> looking for alternative ways of doing 64-bit arithmetics.

I agree. I notice the problem might be due to signed and unsigned. The
FILETIME high or low part if interpreted as 'long double' which is
signed shows negative value as in 'convert_raw_time' function.

Anyway, I will continue to explore this to the best of my abilities.

-dhruva

-- 
Contents reflect my personal views only!