Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 8 Nov 2000 21:38:06 -0500 From: Christopher Faylor To: cygwin@sources.redhat.com Subject: Re: Bug report: gcc + cygwin Message-ID: <20001108213806.A7278@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from Emilian.Medve@motorola.com on Wed, Nov 08, 2000 at 09:05:40PM +0200 On Wed, Nov 08, 2000 at 09:05:40PM +0200, Medve Emilian-EMMEDVE1 wrote: >Thanx for the prompt response. I have some questions regarding your answer. > >How CygWin manages the size of fd table since the same program compiled with >-mno-cygwin says that my Windows allows a process to have only 256 files >opened at a time? winsup/cygwin/dtable.cc contains the fd table handling code. As far as I know, Windows does not impose a handle limit on a process other than system resource limits. >You said that I used a terible method to find out the size of fd table. Do >you know a better method? Can you tell it to me? Well, cygwin really has no upper bounds so you'd have to choose something arbitrary. The normal way of doing this is to use sysconf (_SC_OPEN_MAX). This just returns the current size of the table in cygwin, though. The comments in this code (winsup/cygwin/sysconf.cc) suggest that the NOFILE or OPEN_MAX constants might be better. You could probably just use an arbitrary number like 512, or something, though. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com