From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Build hangs in lisp/gnus.
Date: Sat, 04 Apr 2015 18:43:56 +0300 [thread overview]
Message-ID: <83pp7joq4j.fsf@gnu.org> (raw)
In-Reply-To: <20150404153529.GD4362@acm.fritz.box>
> Date: Sat, 4 Apr 2015 15:35:30 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> 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?
Type "finish" repeatedly s long as it displays the call-stack frames,
then tell here which frame was the last you saw, before it stopped
showing frames.
next prev parent reply other threads:[~2015-04-04 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 14:16 Build hangs in lisp/gnus Alan Mackenzie
2015-04-04 14:32 ` Eli Zaretskii
2015-04-04 15:35 ` Alan Mackenzie
2015-04-04 15:43 ` Eli Zaretskii [this message]
2015-04-04 16:42 ` Alan Mackenzie
2015-04-04 16:56 ` Eli Zaretskii
2015-04-04 19:11 ` Alan Mackenzie
2015-04-05 10:54 ` Alan Mackenzie
2015-04-05 17:22 ` Eli Zaretskii
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=83pp7joq4j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--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.