X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 13 Oct 2009 10:10:38 +0200 From: Corinna Vinschen To: cygwin@cygwin.com, XEmacs developers Subject: Re: Segfault under cygwin 1.7.62 Message-ID: <20091013081038.GA32532@calimero.vinschen.de> Reply-To: cygwin@cygwin.com, XEmacs developers Mail-Followup-To: cygwin@cygwin.com, XEmacs developers References: <87pr8yqmdt.fsf@uwakimon.sk.tsukuba.ac.jp> <20a807210910080843k50c4cbddtb06ad474b3195a03@mail.gmail.com> <87ws35pwbg.fsf@uwakimon.sk.tsukuba.ac.jp> <20a807210910081950v80a4da9ga5ed1265dfca07ef@mail.gmail.com> <416096c60910082305y2f0783a5i95b2adac872831bd@mail.gmail.com> <873a5sn3sk.fsf@uwakimon.sk.tsukuba.ac.jp> <416096c60910100842s44cf8038y9c8a2c4f0b7c8abe@mail.gmail.com> <87aazwkhyl.fsf@uwakimon.sk.tsukuba.ac.jp> <20a807210910121216u71ee04f7o4061480c49f14b06@mail.gmail.com> <87eip8ict7.fsf@uwakimon.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87eip8ict7.fsf@uwakimon.sk.tsukuba.ac.jp> User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Oct 13 05:20, Stephen J. Turnbull wrote: > 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. Actually, no. Cygwin doesn't care for the default locale value itself. It's the system default locale set and returned by setlocale(LC_ALL, "") if none of the locale environment variables is set, per http://www.opengroup.org/onlinepubs/7990989775/xbd/locale.html The net result within Cygwin is the same, the charset is set to UTF-8. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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