Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15559

Re: Running 32 bit program on 64 bit system makes bash etc. look bad

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Eli Schwartz <eschwartz@archlinux.org>
Newsgroups gnu.bash.bug
Subject Re: Running 32 bit program on 64 bit system makes bash etc. look bad
Date Sat, 2 Nov 2019 20:54:11 -0400
Lines 103
Approved bug-bash@gnu.org
Message-ID <mailman.479.1572742463.13325.bug-bash@gnu.org> (permalink)
References <87ftj7m9q9.5.fsf@jidanni.org> <a17ea1c2-79c4-87a0-7084-4c7ffe27e485@archlinux.org>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="m5JKwez6d1S4h0iLeD640Mw4ZNF5R4t7B"
X-Trace usenet.stanford.edu 1572742463 13309 209.51.188.17 (3 Nov 2019 00:54:23 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/simple; d=archlinux.org; s=orion; t=1572742454; bh=ZUO9rdUQobVJQU8XClEroE+r/P+9sOcvIydgE7LRN6s=; h=Subject:To:References:From:Date:In-Reply-To; b=d1hecTlPLrkvgPjvbBsKHtPlJDOiXNOB1lELyGyOqUFr51ZYWZ6lg3YTo8HS5WGwH pIuZ0ID0H3gtMLHyWmgFsWGwKlm7bhHEGDQw79odnzpWqwiakAXMBdheBoky4grn78 kjurVXHoMpMOFYcLo81amO/FE/BD5ovzCaWrUs6L1/vK+HX5HFTKQgjUYw+HFZu8gp RVJktMEt5sUJsEoHu9wU1gcI3Jsse/+Q9abUiBAT62nAVbdMU8RrlEfhvIvZHwKpGW T97g4JaA2xMBMWlv3EjTnZN8gMYzVd6FrLmVLjlP6ZaeJ3HmP8IXdhZ/RzUvdVisFe nATeq4QcgmMJ9Z7JkBxQc6qo4LcGuJIDJwHh9CCWBsHVeE4P6wJ+/pMPnQbb4ovfH/ f6jRb1govd/nMMeStefkQj0qysB3hzi9aRbnCAJ92AtXviFhGmvNgNRygFxCOiZn/7 fSlxwX5Wn4ek7F/KBZt1DALAP4uL5v0BtVob8zOO5CfIoWIAvndo1qjfRUNMowrGrX sQ+6i7bh9VRLjbWPoqCVT6YXywD7eEta+HDhKI7+rCel2vN4P2OnQcVPiXpztHi7aS vacKIRXOtFoqklUMX+JB+hj80a5JBxYzc1B+ItvKOG0oEBsJ+RMIzGF92Zeot47XRm gJPQ+IHD8xW/gSgY/rPZlnow=
X-Clacks-Overhead GNU Terry Pratchett
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0
In-Reply-To <87ftj7m9q9.5.fsf@jidanni.org>
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy]
X-Received-From 88.198.91.70
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <a17ea1c2-79c4-87a0-7084-4c7ffe27e485@archlinux.org>
X-Mailman-Original-References <87ftj7m9q9.5.fsf@jidanni.org>
Xref csiph.com gnu.bash.bug:15559

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On 11/1/19 7:56 PM, 積丹尼 Dan Jacobson wrote:
> $ 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.

This seems like a very complicated way to work around the fact that
you're either downloading mysterious (32-bit) binaries which aren't for
your (64-bit) OS, or installing broken stuff from your package manager
that doesn't pull in the 32-bit support libraries it is supposed to.

And as you cleverly pointed out, "fixing" bash would not "fix" strace or
any of the many other ways it is possible to launch an executable file.
Playing whack-a-mole seems not-fun.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Running 32 bit program on 64 bit system makes bash etc. look bad Eli Schwartz <eschwartz@archlinux.org> - 2019-11-02 20:54 -0400

csiph-web