X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL,TW_DF,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F9F45A1.60500@cornell.edu> Date: Mon, 30 Apr 2012 22:08:33 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: {emacs,emacs-X11,emacs-el}-24.0.96-1 (TEST) References: <4F9F32ED DOT 3030808 AT cs DOT utoronto DOT ca> <4F9F3751 DOT 6000406 AT cs DOT utoronto DOT ca> In-Reply-To: <4F9F3751.6000406@cs.utoronto.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown AT cornell DOT edu - Mon Apr 30 22:08:35 2012 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 4/30/2012 9:07 PM, Ryan Johnson wrote: > On 30/04/2012 8:48 PM, Ryan Johnson wrote: >> On 30/04/2012 4:08 PM, Ken Brown wrote: >>> Test releases of the emacs, emacs-X11, and emacs-el packages >>> (24.0.96-1) are now available. This is a pretest for the upcoming >>> release of emacs-24.1. >>> >>> Emacs users are encouraged to try it and report any problems to the >>> cygwin mailing list. >> I'm experiencing regular seg faults, often while using gdb but not >> always (switching between buffers is another big offender). I'm not >> sure what other information I can provide, other than the EIP=610CF707 >> reported in the .stackdump file... > Caught one in gdb (no symbols, sadly): > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 8128.0x3d0] > 0x0000010c in ?? () > (gdb) bt > #0 0x0000010c in ?? () > #1 0x0054b0ac in ?? () > #2 0x004e4303 in ?? () > #3 0x0054afbe in ?? () > #4 0x004e4e96 in ?? () > #5 0x004e5180 in ?? () > #6 0x004dfbec in ?? () > #7 0x610070d8 in _cygwin_exit_return () from /usr/bin/cygwin1.dll > #8 0x00000003 in ?? () > #9 0x610050dd in _cygtls::call2(unsigned long (*)(void*, void*), void*, > void*) > () from /usr/bin/cygwin1.dll > Backtrace stopped: Not enough registers or memory available to unwind > further > > HTH... I'm reverting for now (I can re-install if you've got specific > ideas to try out) Thanks for testing. I'll try to make debugging symbols available so that you can get a better backtrace. It might be a few days before I get to it. Do you have a recipe that will reliably produce a segfault for you? I've been using emacs-24 for months without any problems (as long as I build without gsettings support, as I did for emacs-24.0.96-1). But I haven't tested gdb-mi for a while. You said you got segfaults even while not using gdb-mi. But did you get segfaults in an emacs session in which you didn't use gdb-mi at all in the entire session? Ken -- 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