From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: "exec" procedures don't handle the optional parameters unbounded situation?
Date: Thu, 15 Dec 2011 20:19:19 +0100 [thread overview]
Message-ID: <877h1xej7s.fsf@gnu.org> (raw)
In-Reply-To: CAPjoZocbzu__+KOmvZf1h9P854HxbAawdR=poM0nHNa9RSi1jg@mail.gmail.com
Hi!
Sorry for the late reply.
Nala Ginrut <nalaginrut@gmail.com> skribis:
> I found "exec" serial procedures didn't check the unbounded optional
> parameters.
> (execlp "ls") ==> segment fault
What you’re seeing here is SIGABRT, not SIGSEGV, preceded by the message:
A NULL argv[0] was passed through an exec system call.
That message comes from Gnulib’s ‘set_program_name’ [0], which is used
by all GNU Coreutils program, and which aborts when argv[0] is NULL.
Thanks,
Ludo’.
[0] http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/progname.c#n53
next prev parent reply other threads:[~2011-12-15 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 9:24 "exec" procedures don't handle the optional parameters unbounded situation? Nala Ginrut
2011-12-15 19:19 ` Ludovic Courtès [this message]
2011-12-16 4:03 ` Nala Ginrut
2011-12-16 23:02 ` Ludovic Courtès
2011-12-17 4:34 ` David Kastrup
2012-01-06 18:02 ` Andy Wingo
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=877h1xej7s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).