On 09/13/2017 08:37 PM, James Clarke wrote: > With the attached patch, qemu-sh4-static now works for file:
I can also confirm that the patch fixes the problem for me. Would be great if it could get merged in one form or another. -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1716767 Title: file(1) fails with "Invalid argument" on qemu-sh4-user Status in QEMU: New Bug description: We recently discovered that file(1) fails on qemu-sh4-user when running on an ELF file: (sid_sh4)root@vs94:/# file /bin/bash /bin/bash: ERROR: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV) error reading (Invalid argument) (sid_sh4)root@vs94:/# Running with "-d" yields more output: (sid_sh4)root@vs94:/# file -d /bin/bash 2>&1 | tail 322: >> 7 byte&,=97,"(ARM)"] 0 == 97 = 0 mget(type=1, flag=0, offset=7, o=0, nbytes=863324, il=0, nc=1) mget/96 @7: \000\000\000\000\000\000\000\000\000\002\000*\000\001\000\000\000\250\317A\0004\000\000\000L(\r\000\027\000\000\0004\000 \000\n\000(\000\032\000\031\000\006\000\000\0004\000\000\0004\000@\0004\000@\000@\001\000\000@\001\000\000\005\000\000\000\004\000\000\000\003\000\000\000t\001\000\000t\001@\000t\001@\000\023\000\000 323: >> 7 byte&,=-1,"(embedded)"] 0 == 18446744073709551615 = 0 [try softmagic 1] [try elf -1] /bin/bash: ERROR: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV) error reading (Invalid argument) (sid_sh4)root@vs94:/# It seems that the comparison above has a bogus (overflown?) value. On actual hardware, it works: root@tirpitz:~> file /bin/bash /bin/bash: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=4dd0e4281755827d8bb6686fd481f8c80ea73e9a, for GNU/Linux 3.2.0, stripped root@tirpitz:~> I have uploaded a chroot with Debian unstable which allows to reproduce the issue: > https://people.debian.org/~glaubitz/sid-sh4-sbuild.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1716767/+subscriptions
