Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Thu, 28 Aug 2003 14:39:43 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: all apps crash at startup with current CVS checkout of cygwin
Message-ID: <20030828183943.GB8547@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20030828100820 DOT GC28930 AT linux_rln DOT harvest> <20030828143400 DOT GC3806 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030828143400.GC3806@redhat.com>
User-Agent: Mutt/1.4.1i

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

Another option is to send cygcheck output as an attachment.  I can't
duplicate this with my home-grown cygiwn or with the last snapshot.

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/