Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 21 Mar 2004 12:36:15 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Minimal test case for Make crash bug Message-ID: <20040321173615.GA27523@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <405C00BF DOT 3090507 AT kegel DOT com> <405C06C4 DOT 7030508 AT kegel DOT com> <405C6C4B DOT 90409 AT kegel DOT com> <405C939E DOT 5020909 AT kegel DOT com> <405D1ACD DOT 4060809 AT kegel DOT com> <405D3CEA DOT 3090006 AT kegel DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <405D3CEA.3090006@kegel.com> User-Agent: Mutt/1.4.1i On Sat, Mar 20, 2004 at 10:57:46PM -0800, Dan Kegel wrote: >Dan Kegel wrote: >>int main(int argc, char **argv) >>{ >> int i; >> for (i=0; ; i++) { >> int fd = open("foo.c", O_RDONLY); >> printf("fd #%d is %d\n", i, fd); >> } >>} >> >>This crashes for me at the 133rd fd unless I run it under gdb ... > >OK, I built a debugging version of cygwin1.dll and dropped it on top of >the normal one, then ran my test program with > export CYGWIN=error_start:C:\\cygwin\\bin\\gdb.exe > ./foo >and hit 'c' and then 'bt' as suggested. Looks like the debugger is a >bit happier with the debugging build. I don't have time to look at it >tonight, but in case it makes any sense to you, here's the backtrace. Can you provide the output from: info dll p alloc_sz p cygheap p cygheap_max I assume that you're using cygwin 1.5.9 and that your mount table is as you reported in your original message. Could you also report on the output of pwd? Thanks, cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/