From: "Ludovic Courtès" <ludo@gnu.org>
To: 38348@debbugs.gnu.org
Cc: Andy Wingo <wingo@igalia.com>
Subject: bug#38348: [2.9.5] Stack overflow when stdout is closed
Date: Thu, 12 Dec 2019 22:46:56 +0100 [thread overview]
Message-ID: <87lfrh43ov.fsf@gnu.org> (raw)
In-Reply-To: <87imna5ymx.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 23 Nov 2019 17:46:30 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> skribis:
> Guile 2.9.5 segfaults from a C stack overflow when you start it with a
> closed stdout:
>
> /gnu/store/7vwf3nhiacxc2jgcg43w22px4ds3rb36-guile-next-2.9.5/bin/guile -c '(pk 1)' >&-
>
> The backtrace looks like this:
>
> (gdb) bt -30
> #312742 0x00007f2ea9b2961f in scm_error (key=wrong-type-arg, subr=subr@entry=0x0, message=message@entry=0x7f2ea9bcafb6 "Wrong type (expecting ~A): ~S",
> args=("output port" #f), rest=rest@entry=(#f)) at error.c:62
> #312743 0x00007f2ea9b299a4 in scm_wrong_type_arg_msg (subr=subr@entry=0x0, pos=pos@entry=0, bad_value=bad_value@entry=#f,
> szMessage=szMessage@entry=0x7f2ea9bc98a5 "output port") at error.c:275
> #312744 0x00007f2ea9b755bd in scm_puts (s=s@entry=0x7f2ea9bd92c0 "Pre-boot error; key: ", port=port@entry=#f) at ports.c:3625
In 2.9.6 the stack overflow is fixed (yay!) but we still get the error
above:
--8<---------------cut here---------------start------------->8---
$ guile --version >&-
Error while printing pre-boot error: wrong-type-arg
Abortita(nekropsio elŝutita)
$ guile --version
guile (GNU Guile) 2.9.6
Copyright (C) 2019 Free Software Foundation, Inc.
License LGPLv3+: GNU LGPL 3 or later <http://gnu.org/licenses/lgpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
--8<---------------cut here---------------end--------------->8---
Ludo’.
next prev parent reply other threads:[~2019-12-12 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 16:46 bug#38348: [2.9.5] Stack overflow when stdout is closed Ludovic Courtès
2019-11-25 8:47 ` Andy Wingo
2019-12-12 21:46 ` Ludovic Courtès [this message]
2020-01-17 13:52 ` 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=87lfrh43ov.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38348@debbugs.gnu.org \
--cc=wingo@igalia.com \
/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).