all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: x86_64 problems/fix (was: alloc.c problem when GC_MARK_STACK is GC_USE_GCPROS_AS_BEFORE)
Date: 21 Jul 2004 23:26:05 +0200	[thread overview]
Message-ID: <m3llhd3vde.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <m3zn65qp58.fsf@ecube.site>

Barry Fishman <barry_fishman@att.net> writes:

> storm@cua.dk (Kim F. Storm) writes:
> 
> > Barry Fishman <barry_fishman@att.net> writes:
> >
> >> I was unable to make any change to alloc.c that would fix the GC_MARK_STACK
> >> problem without later crashes in the build while compiling the lisp
> >> files.
> >
> > Does the following patch work (if you undo the patch you suggested below)?
> >
> [patch skipped]
> 
> That was my first attempt at fixing the problem. The emacs (bootstrap)
> build then failed later on during a lisp compile.  I could not
> diagnose what was causing it, but at the time assumed it was a
> garbage collector problem.
> 
> Trying it again I get the following during a bootstrap build:

I have been running with the patch and GC_USE_GCPROS_AS_BEFORE for a week
now without any problems, and studying the code doesn't indicate to me
what's wrong.

You could try to run the ./temacs command under gdb to see where the
program traps.  You can see the required parameters in the make output.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-07-21 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 22:37 alloc.c problem when GC_MARK_STACK is GC_USE_GCPROS_AS_BEFORE Barry Fishman
2004-07-07  1:08 ` x86_64 problems/fix (was: alloc.c problem when GC_MARK_STACK is GC_USE_GCPROS_AS_BEFORE) Barry Fishman
2004-07-12  9:33   ` Kim F. Storm
2004-07-12 14:24     ` Barry Fishman
2004-07-21 21:26       ` Kim F. Storm [this message]
2004-07-21 22:34   ` Kim F. Storm

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=m3llhd3vde.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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.