From: festerdam@posteo.net
To: 60487@debbugs.gnu.org
Subject: bug#60487: string-ref segfaults with n < 0 on Guile 3.0.8
Date: Mon, 02 Jan 2023 04:12:33 +0000 [thread overview]
Message-ID: <b7b6bcbafd7e0fed8f044fee3ceed060@posteo.net> (raw)
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)
gdb's backtrace is the following:
#0 0x00007ffff7f1bcc5 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#1 0x00007ffff7f26c49 in scm_call_n ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#2 0x00007ffff7e97b29 in scm_apply_0 ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#3 0x00007ffff7f15966 in scm_throw ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#4 0x00007ffff7f174e9 in scm_ithrow ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#5 0x00007ffff7e94735 in scm_error_scm ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#6 0x00007ffff7e94790 in scm_error ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#7 0x00007ffff7ee19e7 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#8 0x00007ffff7ee208b in scm_to_uint64 ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#9 0x00007ffff7f1c5e4 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#10 0x00007ffff7f26c49 in scm_call_n ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#11 0x00007ffff7e93a97 in scm_primitive_eval ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#12 0x00007ffff7e99a86 in scm_eval ()
from /lib/x86_64-linux-gnu/libguile-3.0.so.1
#13 0x00007ffff7ef91c6 in scm_shell () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#14 0x00007ffff7ea865c in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#15 0x00007ffff7e91f6a in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#16 0x00007ffff7f194e8 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#17 0x00007ffff7f26c49 in scm_call_n () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#18 0x00007ffff7e936ea in scm_call_2 () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#19 0x00007ffff7f42292 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#20 0x00007ffff7f0ff4f in scm_c_catch () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#21 0x00007ffff7e942e6 in scm_c_with_continuation_barrier () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#22 0x00007ffff7f14b89 in ?? () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#23 0x00007ffff7c190e7 in GC_call_with_stack_base () from
/lib/x86_64-linux-gnu/libgc.so.1
#24 0x00007ffff7f0fe68 in scm_with_guile () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#25 0x00007ffff7eb1185 in scm_boot_guile () from
/lib/x86_64-linux-gnu/libguile-3.0.so.1
#26 0x000055555555510f in ?? ()
#27 0x00007ffff7c9918a in __libc_start_call_main
(main=main@entry=0x5555555550b0, argc=argc@entry=1,
argv=argv@entry=0x7fffffffe0b8) at
../sysdeps/nptl/libc_start_call_main.h:58
#28 0x00007ffff7c99245 in __libc_start_main_impl (main=0x5555555550b0,
argc=1, argv=0x7fffffffe0b8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe0a8) at
../csu/libc-start.c:381
#29 0x00005555555551aa in ?? ()
next reply other threads:[~2023-01-02 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 4:12 festerdam [this message]
2023-01-02 4:24 ` bug#60488: string-ref segfaults with n < 0 on Guile 3.0.8 festerdam
2023-01-02 9:01 ` Jean Abou Samra
2023-01-16 22:15 ` bug#60487: " Ludovic Courtès
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=b7b6bcbafd7e0fed8f044fee3ceed060@posteo.net \
--to=festerdam@posteo.net \
--cc=60487@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).