From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: bootstrap error Date: Sat, 28 Jan 2006 16:01:40 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1138502229 28289 80.91.229.2 (29 Jan 2006 02:37:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 29 Jan 2006 02:37:09 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 29 03:37:06 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F32R0-0001aF-HH for ged-emacs-devel@m.gmane.org; Sun, 29 Jan 2006 03:36:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F32O3-0002zG-7m for ged-emacs-devel@m.gmane.org; Sat, 28 Jan 2006 21:33:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F2x05-0000hV-GT for emacs-devel@gnu.org; Sat, 28 Jan 2006 15:48:50 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F2wuf-0006as-Ba for emacs-devel@gnu.org; Sat, 28 Jan 2006 15:43:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F2wEG-0006oi-7B for emacs-devel@gnu.org; Sat, 28 Jan 2006 14:59:24 -0500 Original-Received: from [192.114.186.17] (helo=gandalf.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F2qgI-0004YK-O1 for emacs-devel@gnu.org; Sat, 28 Jan 2006 09:03:59 -0500 Original-Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) by gandalf.inter.net.il (MOS 3.7.1-GA) with ESMTP id HSB03675; Sat, 28 Jan 2006 16:01:34 +0200 (IST) Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-8-12.inter.net.il [80.230.8.12]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id COX26667 (AUTH halo1); Sat, 28 Jan 2006 16:01:33 +0200 (IST) Original-To: Alexander Klimov In-reply-to: (message from Alexander Klimov on Sat, 28 Jan 2006 11:50:12 +0200 (IST)) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:49637 Archived-At: > Date: Sat, 28 Jan 2006 11:50:12 +0200 (IST) > From: Alexander Klimov > cc: emacs-devel@gnu.org > > What I wanted to say is that it looks like (what I understand was) the > indian.el problem -- some resource is slowly exhausted and so the > error manifests itself in some random place afterwards. First I get > bootstrap failure at ucs-tables, when I remove ucs-tables I get the > same failure at some next module, when I remove that new module -- > another one failed. My point was that it looks like ucs-tables or > other failed modules have nothing to do with the reason of the error. That is probably so. But I cannot reproduce anything like that on Windows without Cygwin, so you will have to debug this on your machine and tell here your findings. That is the only practical way to debug this. > > Attempt to autoload define-minor-mode while preparing to dump > > > > And then it aborts. So I kinda can reproduce your problem, although > > it doesn't prevent bootstrapping on my system. > > Probably it is some interaction with gdb? I'm not sure. As I explained in a follow-up message, the error message happened because I didn't run temacs with the "bootstrap" argument on the command line. > In my case obtain was called during bootstrap hundreds of time and > in your case it failed after three. There should be no reason for it to call obtain so many times, and moreover, it calls it with the same arguments again and again. Perhaps try downgrading to the previous version of Cygwin--there might be some bug in the latest version. > I have not seen *any* error messages during bootstrap -- it just > silently failed. The silent failure is another puzzle: did it abort? did it exit with a failure indication? Perhaps putting a breakpoint on the lowest-level exit routine you can will shed some light on this. Anyway, thanks for working on this.