From: Linas Vepstas <linasvepstas@gmail.com>
To: 27234@debbugs.gnu.org
Subject: bug#27234: Followup.
Date: Sat, 9 Sep 2017 15:44:11 -0500 [thread overview]
Message-ID: <CAHrUA37zT6FU606vJhDD250nByzpkmj9_DBVvNgjXE3PAdf1sg@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA361VtW9ZOgEbxTYsDi3K7WY4YVaGA=YAK3VQKSVs8Bc_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
The original bug report failed to explain how to trigger the bug. I think
I know of a simple way to trigger the bug, but have not yet created the
simple test-case. I believe that the bug can be triggered like so:
Create some medium-sized "random" (arbitrary) snippet of guile code. Send
it to the guile repl server. Do it again and again, as fast as possible.
The bug will trigger.
By "arbitary/random" I mean some code that is simple but non-repeating:
say, concatenate some random strings, count the number of letters in them,
take the square root -- just do assorted, non-repeating computations that
force the REPL to evaluate some new blob of scheme code every time.
Now, once out of every 5 or 50 times, introduce a bug in the scheme code,
causing the REPL to throw an exception. Using ut8 strings might also be a
required ingredient.
I believe that this will trigger the bug. I believe that the bug is some
unprotected section in the guile interpreter, and a race condition clobbers
the guile stack(s) and it all goes downhill from here.
[-- Attachment #2: Type: text/html, Size: 1244 bytes --]
prev parent reply other threads:[~2017-09-09 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 14:57 bug#27234: Hang in GC, inf loop while walking frame pointers Linas Vepstas
2017-09-09 20:44 ` Linas Vepstas [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=CAHrUA37zT6FU606vJhDD250nByzpkmj9_DBVvNgjXE3PAdf1sg@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=27234@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).