unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Harald Maier <harald@maierh.de>
Cc: 2403@emacsbugs.donarmstrong.com
Subject: bug#2403: 23.0.90; emacs bootstrap under AIX hangs at lisp/international/characters.el
Date: Thu, 26 Feb 2009 15:47:41 -0500	[thread overview]
Message-ID: <jwv1vtlc4p3.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <m2ab89njgn.fsf@ate.maierh> (Harald Maier's message of "Thu, 26 Feb 2009 19:26:00 +0100")

> I digged a little bit deeper to this problem. temacs is in an endless
> loop in the following for loop in the alloca.c file:

> --- alloca.c:5101 ---
> #if (GC_MARK_STACK == GC_MAKE_GCPROS_NOOPS \
>      || GC_MARK_STACK == GC_MARK_STACK_CHECK_GCPROS)
>   mark_stack ();
> #else
>   {
>     register struct gcpro *tail;
> =>  for (tail = gcprolist; tail; tail = tail->next)
>       for (i = 0; i < tail->nvars; i++)
>         mark_object (tail->var[i]);
>   }
> #endif
> ---------------------
> If I examine the values in gdb then I see that the second element of
> gcprolist points to itself in the next element. That's why emacs loops.

> Any idea how to fix that?

No idea.  This should never happen, obviously.  The gcprolist (and its
elements) should only ever be touched by the macros GCPRO<n> and
UNGCPRO, so the only thing that comes to mind is that someone does
GCPRO1 twice in the same block.
You may want to add some

   eassert(gcprolist != &gcpro<n>);

to the GCPRO macros which may catch the bug.  Alternatively, if you look
at the backtrace, the problematic uses of GCPRO<n> should be nearby.

Of course, maybe the problem really is one of the stack being clobbered.


        Stefan






      parent reply	other threads:[~2009-02-26 20:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  5:00 bug#2403: 23.0.90; emacs bootstrap under AIX hangs at lisp/international/characters.el Harald Maier
2009-02-26 18:26 ` Harald Maier
2009-02-26 18:28   ` Harald Maier
2009-02-26 19:35   ` Eli Zaretskii
2009-02-26 20:02     ` Harald Maier
2009-02-27 10:27       ` Eli Zaretskii
2009-03-06 21:19         ` Criveti Mihai
2009-03-06 23:04           ` Criveti Mihai
2009-03-07  1:34             ` Dan Nicolaescu
2009-03-07  4:39             ` Dan Nicolaescu
2009-03-08 14:20               ` Harald Maier
2009-03-08 19:11                 ` Eli Zaretskii
2009-03-09 18:02                 ` Dan Nicolaescu
2009-03-10  6:18                   ` Criveti Mihai
2009-03-10 19:48                     ` Eli Zaretskii
2009-03-11  5:32                   ` Harald Maier
2009-02-26 20:47   ` Stefan Monnier [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=jwv1vtlc4p3.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=2403@emacsbugs.donarmstrong.com \
    --cc=harald@maierh.de \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).