Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 20 Apr 2000 16:22:05 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: PS1, gdb and other trubbels Message-ID: <20000420162205.B2308@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com References: <200004201759.TAA02478@sauerkraut-und-lederhosen.e.kth.se> <20000420144815.A1549@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from lha@stacken.kth.se on Thu, Apr 20, 2000 at 09:59:11PM +0200 On Thu, Apr 20, 2000 at 09:59:11PM +0200, Love wrote: >I have another problem too. I have a program that crashes under cygwin >(works for many other) and I suspenct that the error is in cygwin1.dll >since that is what the debugger in VC claims the error is. Its refences 0x4 >an get a "Application Error". gdb is just confused and can't do the >intresting stacktrace (see below). How do I make sure the error is in my >program and not cygwin1.dll ? > >I can give you a tarboll with binaries that cause the error. Sorry. I definitely don't have time to debug individual problems. Is the stack trace below the result of running the gdb that I just made available or some other version? It looks like an older version of gdb which had this particular problem with stack traces. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com