Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 22 Feb 2001 11:11:25 -0500 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: GCC untrackable crashes Message-ID: <20010222111125.D11175@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: <20010221221500.A8646@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Thu, Feb 22, 2001 at 12:57:07AM -0600 On Thu, Feb 22, 2001 at 12:57:07AM -0600, Mumit Khan wrote: >On Wed, 21 Feb 2001, Christopher Faylor wrote: > >> Hmm. As someone who uses the compiler and debugger on an almost daily basis >> I have to say that I have never seen this behavior on a program that was >> compiled with debugging info (-g). > >Thanks to Kevin's post, here's the smallest buggy, but conforming C++, >testcase I can come up with: > > int > main () > { > char *foo = ""; > delete[] foo; > } When I compile this program with the net release of gcc and debug it with the net release of gdb, it gets a SIGSEGV and stops. I click on "View" and "Stack" and the output is perfectly understandable. I haven't tried specifically with Cygwin 1.1.8 so maybe there is some kind of inexplicable problem with that version of Cygwin. If that is the case then the Cygwin snapshots may work better for people. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple