www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Date: | Wed, 20 Sep 2006 10:34:38 -0400 |
From: | Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: REG : Program received signal SIGSEGV, Segmentation fault |
Message-ID: | <20060920143438.GA26535@trixie.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <OF937662DB DOT C4812EA5-ON652571EF DOT 004DFD99-652571EF DOT 004FBA52 AT indusrad DOT com> |
Mime-Version: | 1.0 |
In-Reply-To: | <OF937662DB.C4812EA5-ON652571EF.004DFD99-652571EF.004FBA52@indusrad.com> |
User-Agent: | Mutt/1.5.11 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Wed, Sep 20, 2006 at 08:00:50PM +0530, Syam Prasad Nagabairu wrote: > > >HI to ALL, > >I am working on HP system with XP OS.The problem is, while running a gdb >debugger the following error occured. >Program received signal SIGSEGV, Segmentation fault. >0x77c47631 in msvcrt!memset () > > >Generally the previous errors of the same kind will display the source file >and the location where it is occuring. But this is a specific issue with >which i am facing trouble. If you're receiving this error, then you probably are not debugging a cygwin program since Cygwin doesn't use msvcrt. It is possible that the 'bt' command will provide you with a stack trace. However, in Windows, stack traces are often problematic since most of the system DLLs do not preserve the frame pointer and gdb does not deal with that very well. So, you can't always trust a back trace when it originates in a system function like memset. 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |