Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 29 Aug 2003 12:06:28 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: all apps crash at startup with current CVS checkout of cygwin Message-ID: <20030829160628.GA13143@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030828100820.GC28930@linux_rln.harvest> <20030828143400.GC3806@redhat.com> <20030829094152.GI28930@linux_rln.harvest> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030829094152.GI28930@linux_rln.harvest> User-Agent: Mutt/1.4.1i On Fri, Aug 29, 2003 at 11:41:52AM +0200, Ronald Landheer-Cieslak wrote: >On Thu, Aug 28, 2003 at 10:34:00AM -0400, Christopher Faylor wrote: >> On Thu, Aug 28, 2003 at 12:08:20PM +0200, Ronald Landheer-Cieslak wrote: >> >With a fresh checkout from cygwin's CVS repo, fresh build, etc. I get this >> >when I start rxvt: >> > >> > 6 [main] rxvt 1912 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION >> > 15845 [main] rxvt 1912 open_stackdumpfile: Dumping stack trace to rxvt.exe.sta >> >ckdump. >> > >> >The stackdump is attached. >> >> Stackdumps of self-built dlls are really not interesting. If you are >> building the dll from scratch then you can always debug the problem with >> a gdb + working DLL build with --enable-debugging. gdb will show you >> exactly where the error is occuring. >> >> Or you can use addr2line to decode the addresses below: ^^ ** >> >$ addr2line -e cygwin1.dll 6107BF59 >/home/RLandheer/cygwin/build/i686-pc-cygwin/winsup/cygwin/../../../../src/winsup/cygwin/sync.cc:75 > >just in case it helps :) -- 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/