X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 4 Mar 2013 14:17:35 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: segfault in recent snapshots Message-ID: <20130304131735.GF2481@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20130302202911 DOT GA1371 AT ednor DOT casa DOT cgf DOT cx> <20130303180626 DOT GA5313 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 4 12:36, Henry S. Thompson wrote: > Christopher Faylor writes: > > >>> And, if it is segfaulting then there is a stackdump file. > >>> Post that. > >> > >>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000 > >>eax=003D0000 ebx=00000000 ecx=7792389A edx=006F017C esi=61006C50 edi=0028CD78 > >>ebp=0028AC88 esp=0028AC4C program=C:\Cygwin\bin\psql.exe, pid 11572, thread main > >>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B > >>Stack trace: > >>Frame Function Args > >>0028AC88 003D0000 (61273B28, 00000000, 00000000, 00000000) > >>0028ACF8 61006CF5 (00000000, 0028CD78, 61006C50, 00000000) > >>End of stack trace > >> > >>Exception: STATUS_ACCESS_VIOLATION at eip=003D0000 > >>eax=003D0000 ebx=00000000 ecx=7792389A edx=0112017C esi=61006C50 edi=0028CD78 > >>ebp=0028AC88 esp=0028AC4C program=C:\cygwin\usr\local\bin\xemacs-21.5-b33.exe, pid 10904, thread main > >>cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B > >>Stack trace: > >>Frame Function Args > >>0028AC88 003D0000 (61273B28, 00000000, 00000000, 00000000) > >>0028ACF8 61006CF5 (00000000, 0028CD78, 61006C50, 00000000) > >>End of stack trace > >> > > > > This address indicates that the error is in user code, so this again > > devolves to something that Marco would likely have to look into. The > > "003D0000" looks like a DLL which has not been properly rebased. > > > > If you can duplicate this under gdb then "info shared" should tell you > > which dll is associated with that address. > > Sorry if I've not understood correctly, but when I catch the segfault > in gdb, info shared doesn't show anything loaded in that address > range: > > (gdb) info shared Since you're running GDB anyway, what does `bt' print when the SEGV occured? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple