From: Ricardo Wurmus <rekado@elephly.net>
To: 46447@debbugs.gnu.org
Subject: bug#46447: segfault with bugnum
Date: Thu, 11 Feb 2021 21:54:38 +0100 [thread overview]
Message-ID: <874kiiqq9d.fsf@elephly.net> (raw)
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:
--8<---------------cut here---------------start------------->8---
$ guile -s foo.scm
;;; note: source file /home/rekado/dev/gx/branches/master/foo.scm
;;; newer than compiled /home/rekado/.cache/guile/ccache/3.0-LE-8-4.4/home/rekado/dev/gx/branches/master/foo.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/rekado/dev/gx/branches/master/foo.scm
;;; compiled /home/rekado/.cache/guile/ccache/3.0-LE-8-4.4/home/rekado/dev/gx/branches/master/foo.scm.go
176561152
$ [env] guile -s foo.scm
176561152
$ [env] guile -s foo.scm
Segmentation fault
$ [env] guile -s foo.scm
C-c C-c # after more than 6 seconds
$ [env] C-c C-c
$ [env] guile -s foo.scm
Segmentation fault
$ [env] guile -s foo.scm
176561152
$ [env] guile -s foo.scm
C-c C-c
$ [env] guile -s foo.scm
176561152
--8<---------------cut here---------------end--------------->8---
--
Ricardo
next reply other threads:[~2021-02-11 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 20:54 Ricardo Wurmus [this message]
2021-02-11 21:03 ` bug#46447: segfault with bugnum tomas
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=874kiiqq9d.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=46447@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).