From: "Ludovic Courtès" <ludo@gnu.org>
To: festerdam@posteo.net
Cc: 60487-done@debbugs.gnu.org
Subject: bug#60487: string-ref segfaults with n < 0 on Guile 3.0.8
Date: Mon, 16 Jan 2023 23:15:31 +0100 [thread overview]
Message-ID: <877cxmktx8.fsf@gnu.org> (raw)
In-Reply-To: <b7b6bcbafd7e0fed8f044fee3ceed060@posteo.net> (festerdam@posteo.net's message of "Mon, 02 Jan 2023 04:12:33 +0000")
Hi,
festerdam@posteo.net skribis:
> The following code results in a segmentation fault on Guile
> 3.0.8-deb+3.0.8-2 (obtained from the Debian repositories):
> (string-ref "my string" -3)
I can reproduce it with 3.0.8, where I get this backtrace:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (string-ref "my string" -3)
Thread 1 "guile" received signal SIGSEGV, Segmentation fault.
0x00007ffff7f419d9 in scm_is_values (x=<optimized out>) at values.h:30
30 values.h: No such file or directory.
(gdb) bt
#0 0x00007ffff7f419d9 in scm_is_values (x=<optimized out>) at values.h:30
#1 vm_debug_engine (thread=0x7ffff75c1d80) at vm-engine.c:974
#2 0x00007ffff7f4c5d9 in scm_call_n (proc=<optimized out>, argv=<optimized out>, nargs=5)
at vm.c:1610
#3 0x00007ffff7eb8571 in scm_apply_0 (proc=#<program 7ffff5c4e960>, args=()) at eval.c:603
#4 0x00007ffff7f3dc8d in scm_throw (key=out-of-range,
args=<error reading variable: ERROR: Cannot access memory at address 0x0>0x7ffff2bb2c30)
at throw.c:262
#5 0x00007ffff7f3dca9 in scm_ithrow (key=<optimized out>, args=<optimized out>,
no_return=<optimized out>) at throw.c:457
#6 0x00007ffff7eb5245 in scm_error_scm (key=key@entry=out-of-range, subr=<optimized out>,
message=message@entry="Value out of range ~S to< ~S: ~S",
args=args@entry=<error reading variable: ERROR: Cannot access memory at address 0x0>0x7ffff2bb2c70, data=data@entry=(4611686018427387901)) at error.c:90
#7 0x00007ffff7eb52a0 in scm_error (key=out-of-range, subr=0x0, message=<optimized out>,
args=<error reading variable: ERROR: Cannot access memory at address 0x0>0x7ffff2bb2c70,
rest=(4611686018427387901)) at error.c:62
#8 0x00007ffff7f02dd7 in range_error (bad_val=bad_val@entry=4611686018427387901,
min=min@entry=<error reading variable: ERROR: Cannot access memory at address 0x0>0x0,
max=#<bignum 7ffff2baeda0>) at numbers.c:6611
#9 0x00007ffff7f04dfb in scm_to_uint64 (arg=4611686018427387901) at integers.c:259
#10 0x00007ffff7f42215 in vm_debug_engine (thread=0x7ffff75c1d80) at vm-engine.c:1533
#11 0x00007ffff7f4c5d9 in scm_call_n (proc=<optimized out>, argv=<optimized out>, nargs=1)
at vm.c:1610
#12 0x00007ffff7eb4457 in scm_primitive_eval (exp=<optimized out>,
exp@entry=((@ (ice-9 control) %) (begin (load-user-init) ((@ (ice-9 top-repl) top-repl)))))
at eval.c:671
#13 0x00007ffff7eba4b6 in scm_eval (
exp=((@ (ice-9 control) %) (begin (load-user-init) ((@ (ice-9 top-repl) top-repl)))),
module_or_state="#<struct module>" = {...}) at eval.c:705
#14 0x00007ffff7f1e3b6 in scm_shell (argc=1, argv=0x7fffffffd058) at script.c:357
--8<---------------cut here---------------end--------------->8---
Fortunately, this was fixed recently in
c0004442b7691f59a0e37869ef288eb26382ad9e.
Thanks!
Ludo’.
prev parent reply other threads:[~2023-01-16 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 4:12 bug#60487: string-ref segfaults with n < 0 on Guile 3.0.8 festerdam
2023-01-02 4:24 ` bug#60488: " festerdam
2023-01-02 9:01 ` Jean Abou Samra
2023-01-16 22:15 ` Ludovic Courtès [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=877cxmktx8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60487-done@debbugs.gnu.org \
--cc=festerdam@posteo.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).