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: Sat, 4 May 2002 11:44:51 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bug in ln / cygwin1.dll Message-ID: <20020504154451.GE29229@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <011901c1f2fb$1fbf5330$0100a8c0 AT advent02> <20020504042742 DOT GI32261 AT redhat DOT com> <00a201c1f360$133f73a0$0100a8c0 AT advent02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00a201c1f360$133f73a0$0100a8c0@advent02> User-Agent: Mutt/1.3.23.1i On Sat, May 04, 2002 at 12:37:30PM +0100, Chris January wrote: >> >When I run 'make -f Makefile.cvs' with QT3, I find that ln segfaults >trying >> >to create a symlink. I've included the output of strace showing the >problem, >> >output of cygcheck and also the stackdump ln produces. I can reproduce >this, >> >so if you need any more information, please ask. The problem occurs with >the >> >latest Cygwin CVS. >> >ln is 'ln (fileutils) 4.1'. >> >cygwin is 'CYGWIN_NT-5.0 ADVENT02 1.3.11(0.52/3/2) 2002-05-03 15:18 i686 >> >unknown' >> >> You're using a locally built version of cygwin. Please run it under gdb >> and pinpoint where the problem is occurring. You may find the techniques >> in how-to-debug-cygwin.txt useful. >As far as I can tell, it's caused by the fact that more than 1024 arguments >are being passed to ln and in exec.cc, argv is declared as 1024 elements. Is >there any reason this limit shouldn't be upped to, say, 2048 elements? If >not, can this change be made in CVS please. Where, specifically, is the segv occurring? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/