From: Neil Jerram <neil@ossau.uklinux.net>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: build errors: 9172 Broken pipe and 9173 Segmentation fault
Date: Thu, 24 Mar 2011 01:45:10 +0000 [thread overview]
Message-ID: <87aagl2swp.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <AANLkTimFpR=ti0UihqCk3ZCch+9O-mLiY87nECKqxZ6W@mail.gmail.com> (Douglas Mencken's message of "Thu, 24 Mar 2011 02:05:06 +0100")
Douglas Mencken <dougmencken@gmail.com> writes:
> GEN guile-procedures.texi
> /bin/bash: line 1: 9172 Broken pipe cat alist.doc
[...]
> 9173 Segmentation fault | GUILE_AUTO_COMPILE=0
> ../meta/uninstalled-env guile-tools snarf-check-and-output-texi >
Hi Douglas,
AFAIK this isn't an already known problem. This is the first point in
the build where the built Guile executable is actually run, so the
problem here may be generic (on powerpc) and not necessarily connected
with the snarf-check-and-output-texi function.
To investigate or help us understand more, you could:
- arrange to get a core dump (maybe with 'ulimit -c unlimited')
- use meta/gdb-uninstalled-guile, and then the 'core-file' command
inside GDB, to look at that core dump
- in particular, use 'thread apply all bt' to get backtraces.
Thanks,
Neil
next prev parent reply other threads:[~2011-03-24 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 1:05 build errors: 9172 Broken pipe and 9173 Segmentation fault Douglas Mencken
2011-03-24 1:45 ` Neil Jerram [this message]
[not found] ` <AANLkTindvcPaJ4qYr7OCvWbitFCzb2oALNO1ya6x0_Y4@mail.gmail.com>
2011-03-29 17:07 ` Douglas Mencken
2011-04-01 9:08 ` Andy Wingo
2011-04-16 11:19 ` Douglas Mencken
2011-04-16 16:01 ` Andy Wingo
2011-04-17 2:34 ` Mark H Weaver
2011-04-18 21:16 ` Ludovic Courtès
2011-04-18 23:45 ` Mark H Weaver
2011-04-21 10:28 ` Andy Wingo
2011-04-17 2:38 ` Mark H Weaver
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aagl2swp.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=dougmencken@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.
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).