From: Linas Vepstas <linasvepstas@gmail.com>
To: 25267@debbugs.gnu.org
Subject: bug#25267: guile-2.2 crash in GC
Date: Sat, 24 Dec 2016 13:00:39 -0600 [thread overview]
Message-ID: <CAHrUA35zacJoWwBscEm8vnFOF9fQeMqhqGtTijWD+W7xtESxxw@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA3516D6fHTSJG7hp1pP26wN2DJ_ubbUEUphp56=BqFZHqQ@mail.gmail.com>
FYI, this is quickly and easily reproducible, happens within seconds,
and hits the same spot every time. Note-to-self (not for general
consumption): my unit test to provoke this is to start the cogserver
and run this shell script:
#!/bin/bash
i=0
while true ; do
let i=$i+1
if [ "$(($i % 2000))" -eq "0" ] ; then
echo loop $i
fi
# echo '(display ctr)' | nc localhost 17001
echo '(NumberNode ctr)' | nc localhost 17001
done
other testing variants are described in
https://github.com/opencog/opencog/issues/2550
next prev parent reply other threads:[~2016-12-24 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 18:43 bug#25267: guile-2.2 crash in GC Linas Vepstas
2016-12-24 19:00 ` Linas Vepstas [this message]
2016-12-24 19:54 ` bug#25267: crashes here only for invalid scheme Linas Vepstas
2017-01-09 21:53 ` bug#25267: guile-2.2 crash in GC Andy Wingo
2017-01-10 6:45 ` Linas Vepstas
2017-03-01 14:43 ` Andy Wingo
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=CAHrUA35zacJoWwBscEm8vnFOF9fQeMqhqGtTijWD+W7xtESxxw@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=25267@debbugs.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.
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).