Mail Archives: cygwin-developers/2002/07/04/11:21:12

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
X-WM-Posted-At:; Thu, 4 Jul 02 16:21:09 +0100
Message-ID: <003101c2236e$6cbdada0$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: "Pavel Tsekov" <cygwin-apps AT cygwin DOT com>
Cc: <cygwin-developers AT cygwin DOT com>
References: <OF9302AC86 DOT 0EB950DE-ON85256BE4 DOT 005579C2 AT isn DOT instinet DOT com> <00b901c21df9$1c9e3df0$0100a8c0 AT advent02> <20020627163750 DOT GA27819 AT redhat DOT com> <010901c21dfa$de6d74e0$0100a8c0 AT advent02> <3D1B5A59 DOT 7090609 AT ece DOT gatech DOT edu> <3D1B92A6 DOT 4020707 AT ece DOT gatech < <001601c22365$9e42eb50$0100a8c0 AT advent02> <14716164963 DOT 20020704162722 AT syntrex DOT com>
Subject: Re: Re[6]: vmstat
Date: Thu, 4 Jul 2002 16:21:07 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

> CJ> uptime reads the /proc files regardless of what options you pass.
> int main(int argc, char *argv[]) {
>   if(argc == 1) print_uptime();
>   if((argc == 2) && (!strcmp(argv[1], "-V"))) display_version();
>   return 0;
> }
> How ?
Try re-compiling with print_uptime commented out. Notice how it works. Now
put print_uptime back in. Notice how it doesn't work, regardless of what
arguments you pass. Magic!
Run it in gdb - notice how it doesn't reach the first line after main().
Notice how stepping assembly instructions the program wanders off into
invalid memory.
Sorry, but I have no idea why this happens. It does *not* happen with my own
build of the Cygwin DLL. With this, all the procps utilities work fine. This
would suggest something is seriously wrong with:
a) the 1.3.12 DLL
b) my build environment
c) a combination of both
It would be greatly appreciated if you could build the package yourself and
see what happens. If you still see the same problem, this would suggest a
problem with the DLL. If not, this would suggest a problem with my build


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019