Re: Build hangs in lisp/gnus.

[Alan Mackenzie]

Hello, Eli.

On Sat, Apr 04, 2015 at 05:32:22PM +0300, Eli Zaretskii wrote:
> > Date: Sat, 4 Apr 2015 14:16:55 +0000
> > From: Alan Mackenzie <address@hidden>

> > With a make bootstrap, my build hangs.  It hangs in the lisp/gnus
> > directory.  When I try to compile the files individually with:

> >     src/emacs -Q -batch -f batch-byte-compile lisp/gnus/gnus-....el

> > , this hangs too.  I've recently experienced this problem in other
> > places too, but compiled them by hand (using Emacs 24) as a workaround.
> > This workaround is inconvenient for such a large number of files.

> The manual command doesn't hang for me (didn't try a full bootstrap).

> If you attach a debugger, do you see where it hangs or infloops?

I restarted the boot strap with

    CFLAGS="-g3 -O0" make bootstrap

(I don't normally have debugging info compiled), leaving out the -j5 flag
for simplicity.  The make process then slogs away, then it hangs trying
to byte-compile allout.el.

I have attached gdb from a running Emacs and typed bt.  The stack is 197
function calls deep; the top few lines look like this:

#0  0x000000000054f45f in builtin_lisp_symbol (index=0) at lisp.h:1075
#1  0x000000000054f5bb in CAR (c=0) at lisp.h:1213
#2  0x00000000005fcfc2 in Fassq (key=1013312, list=0) at fns.c:1449
#3  0x00000000005f2013 in Fmacroexpand (form=14866355, environment=0) at 
eval.c:1023
#4  0x00000000005f5e5d in Ffuncall (nargs=3, args=0x7fff0f1dc3a8) at eval.c:2721
#5  0x000000000063b0d3 in exec_byte_code (bytestr=9955060, vector=9955093, 
maxdepth=42, args_template=2058, nargs=2, args=0x7fff0f1dc938) at bytecode.c:919
#6  0x00000000005f6668 in funcall_lambda (fun=9955013, nargs=2, 
arg_vector=0x7fff0f1dc928) at eval.c:2885
#7  0x00000000005f60d6 in Ffuncall (nargs=3, args=0x7fff0f1dc920) at eval.c:2767
#8  0x000000000063b0d3 in exec_byte_code (bytestr=9955252, vector=9955285, 
maxdepth=114, args_template=1030, nargs=1, args=0x7fff0f1dcf50) at 
bytecode.c:919
#9  0x00000000005f6668 in funcall_lambda (fun=9955205, nargs=1, 
arg_vector=0x7fff0f1dcf48) at eval.c:2885

I've tried xbacktrace, as suggested in etc/DEBUG, but that didn't work.
(I think I've missed some of the necessary prerequisites in skimming over
the file too quickly.)  I'm not very practiced at gdb.

Is there anything else I could usefully do whilst my gdb is still
running?

-- 
Alan Mackenzie (Nuremberg, Germany).