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: Thu, 19 May 2005 22:27:50 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: New call: Please test latest snapshot Message-ID: <20050520022750.GA19369@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050517212147 DOT GM18174 AT calimero DOT vinschen DOT de> <428C7DA1 DOT 3070407 AT familiehaase DOT de> <428D0D92 DOT 4000004 AT familiehaase DOT de> <20050519224952 DOT GJ13760 AT trixie DOT casa DOT cgf DOT cx> <428D2249 DOT 9080000 AT familiehaase DOT de> <428D2392 DOT 2080905 AT familiehaase DOT de> <20050520014137 DOT GB18259 AT trixie DOT casa DOT cgf DOT cx> <20050520022213 DOT GD18259 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050520022213.GD18259@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Thu, May 19, 2005 at 10:22:13PM -0400, Christopher Faylor wrote: >On Fri, May 20, 2005 at 04:17:48AM +0200, Krzysztof Duleba wrote: >>Christopher Faylor wrote: >> >>> >> Program exited normally. >>> >> (gdb) >>> > >>> >Well, that's the funny thing about Cygwin's gdb. >>> >>>No, that's the funny thing about debugging in general. There's nothing >>>special about cygwin's gdb. >> >>Really? I'd expect something more like this: >> >>(gdb) run Starting program: /home/jsim/k/kd209203/ab >> >>Program received signal SIGABRT, Aborted. 0x40142841 in kill () from >>/lib/libc.so.6 > >You'd expect gdb to report a SIGABRT when the program exhibits a SIGSEGV >outside of gdb? That's odd. > >My point, since you missed it, is that debugging sometimes changes the >execution environment enough so that things "work" inside of a debugger >even though they fail when being debugged. This can happen on cygwin or >linux or Tru64. > >I do have to say, that Windows may be unique in that it enforces >serialized thread execution on debugged programs so this may either >mask or cause problems. I don't know if any UNIX platform does that or >not. If not, I'd have to retract what I said and say that there is >something special about cygwin (and any other windows debugger) in that >respect. Oh, and in the interests of full disclosure, I also have to say that cygwin's gdb does not understand anything but windows signals. Although that doesn't have anything to do with what was being reported, I suspect that this may be where the above confusion is coming from. This has nothing to do with a program that reports a SIGSEGV only when not being debugged, though. 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/