From: ouzb65ty <ouzb65ty@protonmail.ch>
To: 32240@debbugs.gnu.org
Subject: bug#32240: Segfault when execlp vim/nano
Date: Sat, 21 Jul 2018 12:26:30 -0400 [thread overview]
Message-ID: <UrzCbf8ybgZ260RuIHtJ6G_aK-xXHDHcmyszD_LZzsHYWp9vrVWeLs8IXw9TJbozu4ILWJ7ZvCnLOQ5VHsWY8fhznMWucqzNPYHu-UwOGg8=@protonmail.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
Hello,
When I call (execlp "vim") or (execlp "nano") in Guile :
Fatal error 11: Segmentation fault[1] 31380 segmentation fault guile test.scm
Guile --version :
guile (GNU Guile) 2.2.3
Vim --version :
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 4 2017 18:14:54)
Nano --version :
GNU nano version 2.0.6 (compiled 14:26:45, Oct 14 2016)
uname -a :
Darwin e1r5p17.42.fr 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
My .guile is empty, I think it's probably a bug with termcaps..
[-- Attachment #2: Type: text/html, Size: 834 bytes --]
next reply other threads:[~2018-07-21 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 16:26 ouzb65ty [this message]
2018-08-02 15:03 ` bug#32240: Segfault when execlp vim/nano Mark H Weaver
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='UrzCbf8ybgZ260RuIHtJ6G_aK-xXHDHcmyszD_LZzsHYWp9vrVWeLs8IXw9TJbozu4ILWJ7ZvCnLOQ5VHsWY8fhznMWucqzNPYHu-UwOGg8=@protonmail.ch' \
--to=ouzb65ty@protonmail.ch \
--cc=32240@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).