GNU bug report logs - #32240
Segfault when execlp vim/nano

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32240 in the body.
You can then email your comments to 32240 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ouzb65ty <ouzb65ty <at> protonmail.ch>
To: "bug-guile <at> gnu.org" <bug-guile <at> gnu.org>
Subject: Segfault when execlp vim/nano
Date: Sat, 21 Jul 2018 12:26:30 -0400

[Message part 1 (text/plain, inline)]

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..

[Message part 2 (text/html, inline)]

Message #8 received at 32240 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: ouzb65ty <ouzb65ty <at> protonmail.ch>
Cc: 32240 <at> debbugs.gnu.org
Subject: Re: bug#32240: Segfault when execlp vim/nano
Date: Thu, 02 Aug 2018 11:03:27 -0400

Hi,

ouzb65ty <ouzb65ty <at> protonmail.ch> writes:

> When I call (execlp "vim") or (execlp "nano") in Guile :
> Fatal error 11: Segmentation fault[1]    31380 segmentation fault  guile test.scm

When calling the 'exec*' procedures, in both Scheme and C, you should
pass at least two arguments.  The first argument is the program to run,
and the second argument will become argv[0] in the executed program.
Normally this should be the program name again, although in some cases
it is useful to pass a different value as argv[0].

Note that in the Guile manual, the entry for 'execlp' begins by saying
that it's "Similar to 'execl', however ...", and the description of
'execl' states: "If ARG is missing, FILENAME is executed with a null
argument list, which may have system-dependent side-effects."

On my GNU/Linux system, I see this:

  scheme@(guile-user)> (execlp "ls")
  A NULL argv[0] was passed through an exec system call.
  Aborted

Based on your report, I guess that on Darwin it leads to a segfault.

In any case, you are using 'execlp' incorrectly.  It might be that we
should raise an error at the Scheme level if these procedures are called
with only one argument.

Anyway, does it work if you run (execlp "vim" "vim") instead?

      Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.