all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ryan Yeske <rcyeske@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: problems building trunk in OpenBSD/i386
Date: Thu, 12 Jul 2007 07:07:37 -0400	[thread overview]
Message-ID: <E1I8wWH-0001Xl-Rm@fencepost.gnu.org> (raw)
In-Reply-To: <874pkaezdu.fsf@tarn.lan> (message from Ryan Yeske on Thu, 12 Jul 2007 02:37:33 -0700)

> Date: Thu, 12 Jul 2007 02:37:33 -0700
> From: Ryan Yeske <rcyeske@gmail.com>
> 
> 
> cvs update -A
> ./configure
> make bootstrap
> 
> I get the error:
> 
> ./temacs --batch --load loadup bootstrap
> pid 17656: Fatal error 'Cannot create kernel pipe' at line 200 in file /usr/src/lib/libpthread/uthread/uthread_init.c (errno = 24)
> *** Signal 6
> 
> EMACS_22_BASE is the last version that I know builds fine on this platform.
> 
> Advice on how to proceed in debugging this appreciated.

The backtrace indicates there's infinite recursion in gmalloc.c:

> #365 0x08184f6d in __malloc_initialize () at gmalloc.c:615
> #366 0x081856c1 in malloc (size=3072) at gmalloc.c:982

These two lines repeat themselves again and again, with calls to other
functions interspersed in between.

I'm guessing that the infinite recursion causes Emacs to eventually
run out of runtime stack, and then it dies with the above weird
message, which really tells you that the program is in deep trouble.

If you can step through the code in question with GDB and try to
understand why it recurses, it will help.

  reply	other threads:[~2007-07-12 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  9:37 problems building trunk in OpenBSD/i386 Ryan Yeske
2007-07-12 11:07 ` Eli Zaretskii [this message]
2007-07-12 17:22   ` Ken Raeburn
2007-07-13  7:23     ` Jan Djärv
2007-07-20  1:18       ` Ken Raeburn
2007-07-20  6:43         ` Jan Djärv

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=E1I8wWH-0001Xl-Rm@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rcyeske@gmail.com \
    /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.