From: Neil Jerram <neil@ossau.uklinux.net>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: intermittent segfaults in master
Date: Tue, 03 Nov 2009 23:58:45 +0000 [thread overview]
Message-ID: <87d43z88ju.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <7B1681AC-62AE-4F28-9286-4F25BDEB5D0F@raeburn.org> (Ken Raeburn's message of "Sat, 24 Oct 2009 17:56:52 -0400")
Ken Raeburn <raeburn@raeburn.org> writes:
> On Oct 24, 2009, at 09:30, Andy Wingo , n@a-pb-sasl-sd.pobox.com wrote:
>> I have been experiencing intermittent segfaults recently, as I
>> worked on
>> wip-case-lambda. They would almost always go away immediately -- as
>> in,
>> while rebuilding guile, the process would stop because of a segfault,
>> but I could type make again and it would succeed.
>
> I've been seeing intermittent faults too, while working on the trunk
> and building with -DSCM_DEBUG=1.
FWIW I got a segfault that could be this same problem, in my build on
Monday morning:
cat alist.doc arbiters.doc [...] regex-posix.doc | GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools snarf-check-and-output-texi > guile-procedures.texi || { rm guile-procedures.texi; false; }
/bin/sh: line 1: 6408 Broken pipe cat alist.doc arbiters.doc [...] regex-posix.doc
6409 Segmentation fault | GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools snarf-check-and-output-texi > guile-procedures.texi
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory `/home/neil/SW/Guile/ovnight/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/neil/SW/Guile/ovnight/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/neil/SW/Guile/ovnight'
make: *** [all] Error 2
Interestingly, the build then tries to run the built guile again almost
immediately, for a different purpose, and that failed too:
=== API listing
../maint/make-snap: line 3: 6445 Segmentation fault $uninstalled_env ../maint/objd.scm
Maybe it was just unlucky to fault twice, but maybe there's a hint here
that tendency-to-fault could be a property of a particular built guile.
Neil
prev parent reply other threads:[~2009-11-03 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 13:30 intermittent segfaults in master Andy Wingo, n
2009-10-24 21:56 ` Ken Raeburn
2009-11-03 23:58 ` Neil Jerram [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d43z88ju.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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.
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).