Re: old bootstrap error emerges again

[Dieter Deyke]

Eli Zaretskii <address@hidden> writes:

>> From: Dieter Deyke <address@hidden>
>> Cc: address@hidden, address@hidden
>> Date: Sun, 19 Mar 2006 07:44:28 -0700
>> 
>> (gdb) xbacktrace
>> "ad-real-documentation"
>> "ad-subr-arglist"
>> "ad-arglist"
>> "ad-make-advised-definition"
>> "ad-activate-advised-definition"
>> "ad-activate"
>
> Thanks.  These "ad-*" functions in the Lisp backtrace look strange:
> they seem to indicate that defadvice is used somewhere, but I cannot
> see any such defadvice's in the lisp/url directory.  Can you look
> around and try to find where are those defadvice's?
>
>> "byte-code"
>> "require"
>> "byte-code"
>> "load"
>> "load-library"
>
> Also, it would be good to know what package is being loaded in the
> last line above, which says "load-library", and what feature is being
> required in the "require" line before that.  Can you try to find out?
> The way to do that is identify the frames in the C backtrace that
> correspond to these lines in the Lisp backtrace.  For example, the
> innermost call to Frequire would probably correspond to the "require"
> line.  Then print the first argument (with `pr') and see what it is.
> For load-library, the "load" (Fload in C) line that preceeds it will
> tell you via its 1st arg what file is being loaded.
>
> Perhaps this information will show where do those ad-* things come
> from.
>
> Thanks again for working on this.

The lowest Fload I found had a first arg of "uniquify", I do not know
how to decode the args of the Frequire calling it.  feature showed up
as 0, and filename as nil.  The next Fload higher up had an first arg
of "emacsrc".  Makes me think, does bootstrapping emacs read the
~/.emacsrc file I have?

May be we can speed up debugging by hooking up via IM or IRC, and you
provide me with lines I paste into the debugger, and I will paste back
results.

-- 
Dieter Deyke
mailto:address@hidden mailto:address@hidden mailto:address@hidden
Vs lbh pna ernq guvf, lbh unir jnl gbb zhpu gvzr.