all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bootstrap error
Date: Sat, 28 Jan 2006 16:01:40 +0200	[thread overview]
Message-ID: <uzmlgxxh7.fsf@gnu.org> (raw)
In-Reply-To: <TheMailAgent.60590a87522fa@2cf673661b751e3314e5f> (message from Alexander Klimov on Sat, 28 Jan 2006 11:50:12 +0200 (IST))

> Date: Sat, 28 Jan 2006 11:50:12 +0200 (IST)
> From: Alexander Klimov <ask@eitan.edu>
> 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.

  reply	other threads:[~2006-01-28 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-25 13:17 bootstrap error Alexander Klimov
2006-01-25 17:46 ` Eli Zaretskii
2006-01-26 10:21   ` Alexander Klimov
2006-01-27 13:25     ` Eli Zaretskii
2006-01-28  9:50       ` Alexander Klimov
2006-01-28 14:01         ` Eli Zaretskii [this message]
2006-01-29  8:08           ` Alexander Klimov
2006-01-29 19:37             ` Eli Zaretskii
2006-01-30  9:11               ` Alexander Klimov
2006-01-30 11:38                 ` Corinna Vinschen
2006-01-29 17:51           ` Alexander Klimov
2006-01-27 20:37     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2007-08-19  3:17 merging etc Miles Bader
     [not found] ` <200708211523.l7LFNnVl000876@oogie-boogie.ics.uci.edu>
     [not found]   ` <buo3aycknp8.fsf@dhapc248.dev.necel.com>
     [not found]     ` <200708220820.l7M8KbIt026014@oogie-boogie.ics.uci.edu>
     [not found]       ` <fc339e4a0708220237v3b90ec6fwde90eba1ca936e91@mail.gmail.com>
2007-08-22 11:55         ` Miles Bader
2007-08-22 15:33           ` Stefan Monnier
2007-08-23  0:19             ` Juri Linkov
2007-08-23 20:58               ` Richard Stallman
2007-08-24  8:01                 ` joakim
2007-08-24  8:46                   ` Leo
2007-08-24 10:08                     ` David Kastrup
2007-08-24 10:41                       ` Bootstrap error B. Anyos
2016-10-02 19:48 bootstrap error Colin Baxter
2016-10-02 20:22 ` Philipp Stephani
2016-10-03  5:25   ` Colin Baxter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uzmlgxxh7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.