delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
From: | Steffen Sledz <sledz AT zone42 DOT org> |
Subject: | Re: [ANNOUNCEMENT] [test-version] emacs-22.1-3/emacs-el-22.1-3/emacs-X11-22.1-3 |
Date: | Sun, 29 Jul 2007 18:53:46 +0200 |
Lines: | 37 |
Message-ID: | <1185728034.240476@alpaka.in-berlin.de> |
References: | <46AB55EB DOT 3000304 AT aim DOT com> |
Mime-Version: | 1.0 |
User-Agent: | Thunderbird 2.0.0.5 (X11/20070719) |
In-Reply-To: | <46AB55EB.3000304@aim.com> |
Cache-Post-Path: | alpaka.in-berlin.de!unknown AT alpaka DOT in-berlin DOT de |
X-Cache: | nntpcache 3.0.1 (see http://www.nntpcache.org/) |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
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 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Harig schrieb: > If you discover a repeatable set of steps that you can follow that will > cause Emacs to crash, would you please post those to this list? They > could be used as a test to tell whether Emacs has been built correctly. > In addition, your steps might be tested with Emacs on another platform > (most commonly, a UNIX-like system) to determine whether the problem is > specific to the Cygwin implementation of Emacs. Yes, that would be really helpfully. > My guess is that the problem that you are seeing cannot be resolved > easily. Here are three approaches that might be taken, none of which > is trivial: I completely agree. > 1. Identify the C code in the Emacs 22 source that needs to be > "back-ported" to gcc 3.4.4 so that the problem you are seeing > does not occur. A patch could then be applied to Emacs 22 so > that it could run error free on Cygwin. I'll try to setup a debug environment to go this way. But I cannot guarantee for fast results. So if someone else is making gcc4 ready for cygwin, I wouldn't be averse to it. :) Steffen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGrMYZlSfCk8EgCzgRAjSHAJ45IPIS0tHh6cMou2pwM+YZ8A9LvACfVy38 7eGqEwABwvTFRFjoVi9Yc+0= =4bA6 -----END PGP SIGNATURE----- -- 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 |