From: <tomas@tuxteam.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 46447@debbugs.gnu.org
Subject: bug#46447: segfault with bugnum
Date: Thu, 11 Feb 2021 22:03:02 +0100 [thread overview]
Message-ID: <20210211210302.GB5951@tuxteam.de> (raw)
In-Reply-To: <874kiiqq9d.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
On Thu, Feb 11, 2021 at 09:54:38PM +0100, Ricardo Wurmus wrote:
> This program sometimes causes Guile 3.0.5 to segfault:
>
> (define a (expt 2 (expt 3 (expt 4 2))))
> (display (remainder a 1000000000))
> (display "\n")
>
> And sometimes this program doesn’t terminate. Here’s an example
> session with the program saved to foo.scm:
The first expr alone seems to segfault for me (Guile 3.0.4.38-64c894-dirty)
repeatably (well, that means 5 times in a row ;)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2021-02-11 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 20:54 bug#46447: segfault with bugnum Ricardo Wurmus
2021-02-11 21:03 ` tomas [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=20210211210302.GB5951@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=46447@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).