From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8167 invoked by alias); 19 Dec 2016 05:48:19 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22238 Received: (qmail 5609 invoked from network); 19 Dec 2016 05:48:19 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f173.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.217.173):SA:0(-0.0/5.0):. Processed in 1.140848 secs); 19 Dec 2016 05:48:19 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.173 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=9UmiApCd/MOEcYsDt6iM45d7Bpo6grzuS2Zz5YxQ9i0=; b=YExULzfpxnD54XG81gVzAx6xBPot0Puqsh0HqZb0vBekxY0Jpr4xKfddPI7vNBO2Nv e+Ea1dpgR6BkUDlbz/AumDjdqFG2XJbvmQWvyPU3C6gPe+EJs5dnodelFtWmfCNMXux3 wimD7gLonbw0jSLHKU+YO15s3WtNAP2+vA58cdoHbRV4qtUXKe4KElGCOw4r2UuZZhn2 ab4ULHgamue1k61et0hLsQrU1YXfzQoVe2p9ixA9EhKLEO1RAHbSwhrVpllJyhsPkP+x 3D7IZFgqNLP4nTZocYzDSENvke7qy2YTfXjw22czru7AETEGZnK9ElxR7Z7e6G/TjaA5 XCJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=9UmiApCd/MOEcYsDt6iM45d7Bpo6grzuS2Zz5YxQ9i0=; b=CX4/xmkgfiuAmsQWf0VM3zK0R5dd0bnGKVBDA0rX549udzidn/wMAKaaWefRUy9+8/ rpJ9HrVczIwiq+GmP4xhQhvYA/HPe9qqcCWrkPXDDKjONAsjgR76qJzzw0deIf9TqNsy RwsWDoFa0bngFDHimNefniob/0Sa7tmkfrtfpNEvVfWeGl7RNFqTmNeUNKhbWiwXHalT pp4Eth58pGjBF/VW5nWIcAXV6Z5btrcuEDZMjb2RswEvFvw9rHqkHFlbLU/pmjOT2n6l GSAX+V1TDHr2quVh4+JFMNgFULHM44LiTBlsTMupZPzVPeJkRVB1SV4R0hWMNJNSa7dJ YFcw== X-Gm-Message-State: AKaTC013Qzwf7omTYAiUd0FxqJUYNSE8DkqINzme83JiWNVAqUE9aQ7dsh7D/y42DHANXQ== X-Received: by 10.176.3.143 with SMTP id 15mr9396802uau.10.1482126491782; Sun, 18 Dec 2016 21:48:11 -0800 (PST) From: Bart Schaefer Message-Id: <161218214811.ZM5814@torch.brasslantern.com> Date: Sun, 18 Dec 2016 21:48:11 -0800 In-Reply-To: <9da2ae82-ac3f-6ee3-5452-5a008cf129e7@eastlink.ca> Comments: In reply to Ray Andrews "Re: trapped in bash" (Dec 18, 8:29pm) References: <58540944.3030706@eastlink.ca> <20161216215117.GF2023@pug.qqx.org> <58546D36.5050908@eastlink.ca> <161216150556.ZM4016@torch.brasslantern.com> <58559FC0.3080501@eastlink.ca> <161217124354.ZM7815@torch.brasslantern.com> <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca> <20161218150628.GB9158@fujitsu.shahaf.local2> <5856B133.9010602@eastlink.ca> <20161219003219.GA21509@fujitsu.shahaf.local2> <161218183056.ZM5304@torch.brasslantern.com> <9da2ae82-ac3f-6ee3-5452-5a008cf129e7@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: trapped in bash MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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. 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.