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 17:41:30 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: PS1, gdb and other trubbels Message-ID: <20000420174130.B3346@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> <20000420162205.B2308@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 10:35:14PM +0200 On Thu, Apr 20, 2000 at 10:35:14PM +0200, Love wrote: >Chris Faylor writes: > >> >I can give you a tarboll with binaries that cause the error. >> >> Sorry. I definitely don't have time to debug individual problems. > >Sure, I'll happly try to find it out myself, I currenly trying to build a >libcygwin1.dll with debugging symbols. You should be able to set breakpoints in gdb to find out where the problem is occurring. The fact that cygwin shows up on a stack trace does not mean that the problem is in cygwin. Cygwin intercepts all of the Windows "signals" in order to properly emulate UNIX signals. If I were you, I would just debug your program in the normal way before going to the effort of building cygwin. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com