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: Sun, 1 Dec 2002 01:03:54 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gdb received signal SIGSEGV before even entering main! Message-ID: <20021201060354.GA15020@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4 DOT 3 DOT 1 DOT 2 DOT 20021130235227 DOT 02823400 AT pop DOT rcn DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.1.2.20021130235227.02823400@pop.rcn.com> User-Agent: Mutt/1.5.1i On Sat, Nov 30, 2002 at 11:55:18PM -0500, Larry Hall (RFK Partners, Inc) wrote: > >At 12:55 AM 11/29/2002, jing DOT dong AT attbi DOT com wrote: >>The program I ran gdb on a very standard hello world program, it >>crashes even before main is entered. Anybody have an idea how to solve >>this problem? Any help is appreciated. > >I think you'll find some help for this in the email archives. For >details, do a quick search and see the previous discussions. If you're >less interested in the details, just type "cont" and continue running >gdb. In the future, it's worthwhile for you to check the email >archives prior to posting, in case the issue you have has been >discussed previously. FWIW, I think this problem was fixed in 1.3.16. So, if this is a problem it probably is due to an older version of cygwin. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/