X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: "Stephen J. Turnbull" To: Vin Shelton Cc: cygwin AT cygwin DOT com, Andy Koppe , XEmacs developers Subject: Re: Segfault under cygwin 1.7.62 In-Reply-To: <20a807210910121216u71ee04f7o4061480c49f14b06@mail.gmail.com> References: <20a807210910071714t45136fd7hc36108c990377bc4 AT mail DOT gmail DOT com> <87pr8yqmdt DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <20a807210910080843k50c4cbddtb06ad474b3195a03 AT mail DOT gmail DOT com> <87ws35pwbg DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <20a807210910081950v80a4da9ga5ed1265dfca07ef AT mail DOT gmail DOT com> <416096c60910082305y2f0783a5i95b2adac872831bd AT mail DOT gmail DOT com> <873a5sn3sk DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <416096c60910100842s44cf8038y9c8a2c4f0b7c8abe AT mail DOT gmail DOT com> <87aazwkhyl DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <20a807210910121216u71ee04f7o4061480c49f14b06 AT mail DOT gmail DOT com> Date: Tue, 13 Oct 2009 05:20:52 +0900 Message-ID: <87eip8ict7.fsf@uwakimon.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Vin Shelton writes: > The new behavior is different, but the problem is not yet fixed. OK. It's possible that there remain problems in Cygwin, but the probability of an XEmacs bug is increasing. New backtraces would be useful, I think, unless Aidan has a guess offhand. > 4. But when I try to run that XEmacs under gdb, I get different > results: gdb doesn't detect a segfault, and the test seems to run to > completion: That could be a Cygwin or GCC problem then, I don't see why running under GDB would prevent the crash. > Unexpected error (invalid-argument "Invalid (GNU Emacs) key format > (see doc of define-key)" C-f9) while executing byte-compiled code. That could be memory corruption; I don't see where keystrokes would be coming in. Maybe Aidan knows. > Do I need some additional cygwin changes other than the dll? Corinna > - I noticed that you changed the "DEFAULT_LOCALE" in > include/cygwin/config.h (DEFAULT_LOCALE) to "C.UTF-8". Do I need to > import that change into my compile-time environment somehow? Or is > there an environment variable that needs to be set to alter runtime > behavior? That should not affect XEmacs behavior. If changing the locale variables makes a difference, then it's in Cygwin, I think. -- 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