Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson Newsgroups: gnu.bash.bug Subject: Running 32 bit program on 64 bit system makes bash etc. look bad Date: Sat, 02 Nov 2019 07:56:46 +0800 Lines: 37 Approved: bug-bash@gnu.org Message-ID: References: <87ftj7m9q9.5.fsf@jidanni.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: usenet.stanford.edu 1572653571 30444 209.51.188.17 (2 Nov 2019 00:12:51 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org X-Sender-Id: dreamhost|x-authsender|jidanni@jidanni.org X-Sender-Id: dreamhost|x-authsender|jidanni@jidanni.org X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jidanni@jidanni.org X-MailChannels-Auth-Id: dreamhost X-Society-Rock: 5fac0c5625e5e48e_1572653558042_564089222 X-MC-Loop-Signature: 1572653558042:113425494 X-MC-Ingress-Time: 1572653558042 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jidanni.org; h=from:to :subject:date:message-id:mime-version:content-type; s= jidanni.org; bh=VGX+rAQa9PfoImMWsfBuk8K+xTg=; b=CUK3WiCxN9ln8viP 5LlXqf7qz5FAr/N1HXHbXTWcQpfU3sums1VSFTdC92tterxlw1MXeS1+48kqufIc beL8/04T8b2Hep5GTPwjltejdqWDypvtXuWps0BHoFHnP+3eg3PnsGPGciyDqqFX X1LdkUJ3HBdF2Sr+JEGLjCYlm5c= X-DH-BACKEND: pdx1-sub0-mail-a47 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.212.17 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <87ftj7m9q9.5.fsf@jidanni.org> Xref: csiph.com gnu.bash.bug:15555 $ mapping/taipower/pole2tm bash: mapping/taipower/pole2tm: No such file or directory Must be a bash bug! Proof: $ ls -l mapping/taipower/pole2tm -rwxr-xr-x 1 jidanni jidanni 11290 2012-06-19 mapping/taipower/pole2tm But wait, $ strace mapping/taipower/pole2tm execve("mapping/taipower/pole2tm", ["mapping/taipower/pole2tm"], 0x7ffd53416200 /* 58 vars */) = -1 ENOENT (No such file or directory) strace: exec: No such file or directory +++ exited with 1 +++ Must also be a strace bug... Ah, $ file mapping/taipower/pole2tm mapping/taipower/pole2tm: ELF 32-bit LSB executable... but we are running it on $ arch x86_64 Anyway, perhaps somebody could submit a kernel bug, telling them to somehow make bash, etc. look less bad, by a clearer error message, as I suppose bash cannot always catch such cases, to make a better error message. In fact maybe bash could catch it (expensive?): First "stat" the file. If it doesn't exist bash should make its own message bash: /tmp/abce: No such file or directory If it does, then bash should be prepared to catch the kernel's message (which is referring to a *different* file, which yes, actually does not exist.) Whereupon bash could make a better error message.