From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: trapped in bash
Date: Mon, 19 Dec 2016 08:26:43 -0800 [thread overview]
Message-ID: <ab7aeb33-d091-6602-8baa-cce92300d289@eastlink.ca> (raw)
In-Reply-To: <161218214811.ZM5814@torch.brasslantern.com>
On 18/12/16 09:48 PM, Bart Schaefer wrote:
> On Dec 18, 8:29pm, Ray Andrews wrote:
> }
> } Not for me to say, but it seems to me that the simple fact that a file
> } exists or does not exist is simple enough to determine
>
> Well, yes.
>
> The shell finds the file, because it's responsible for path search.
Exactly, I'd expect zsh to handle that with an appropriately helpful
message, but past that point I quite understand that it's not the
shell's affair. Mind, even subsequent error messages might be preceded
by 'execve()' reports: ...' or something like that, it would just make
further diagnosis a bit faster. In my situation I'd be angling for
something like: "Error: binary file '/aa/bb/xxx' is not executable.
execve() reports error #54321: "file not found".
>
> It then forks, and the child process passes the full path to execve(),
> which replaces the child shell with the kernel code that is supposed
> to start up the new executable.
>
> That kernel code then fails for whatever reason -- in this case, it's
> because the 32-bit library is not found -- and returns a nonzero
> numeric exit code to the parent shell.
>
> The parent shell prints the message associated with that error code.
> It isn't responsible for guessing what caused the error; there could
> for example have been additional rounds of finding and exec'ing other
> paths of which the parent has no knowledge, before a final exit.
>
next prev parent reply other threads:[~2016-12-19 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 15:33 Ray Andrews
2016-12-16 21:51 ` Aaron Schrab
2016-12-16 22:39 ` Ray Andrews
2016-12-16 23:05 ` Bart Schaefer
2016-12-17 20:27 ` Ray Andrews
2016-12-17 20:43 ` Bart Schaefer
2016-12-17 22:40 ` Ray Andrews
[not found] ` <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca>
2016-12-18 15:06 ` Daniel Shahaf
2016-12-18 15:54 ` Ray Andrews
2016-12-19 0:32 ` Daniel Shahaf
2016-12-19 2:30 ` Bart Schaefer
2016-12-19 4:29 ` Ray Andrews
2016-12-19 5:48 ` Bart Schaefer
2016-12-19 16:26 ` Ray Andrews [this message]
[not found] ` <ab7aeb33-d091-6602-8baa-cce92300d289__26556.3400615521$1482166729$gmane$org@eastlink.ca>
2016-12-19 17:47 ` Daniel Shahaf
2016-12-17 23:16 ` Jim
2016-12-17 23:38 ` Ray Andrews
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab7aeb33-d091-6602-8baa-cce92300d289@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).