diff options
Diffstat (limited to 'results/classifier/118/permissions/1527765')
| -rw-r--r-- | results/classifier/118/permissions/1527765 | 183 |
1 files changed, 183 insertions, 0 deletions
diff --git a/results/classifier/118/permissions/1527765 b/results/classifier/118/permissions/1527765 new file mode 100644 index 000000000..136ddab8d --- /dev/null +++ b/results/classifier/118/permissions/1527765 @@ -0,0 +1,183 @@ +permissions: 0.851 +graphic: 0.848 +debug: 0.822 +assembly: 0.817 +performance: 0.807 +semantic: 0.800 +device: 0.800 +peripherals: 0.799 +arm: 0.788 +virtual: 0.787 +boot: 0.779 +register: 0.777 +KVM: 0.763 +PID: 0.760 +user-level: 0.757 +hypervisor: 0.750 +socket: 0.743 +vnc: 0.735 +risc-v: 0.734 +architecture: 0.729 +VMM: 0.716 +network: 0.716 +files: 0.715 +kernel: 0.702 +TCG: 0.701 +ppc: 0.680 +mistranslation: 0.542 +x86: 0.541 +i386: 0.514 + +sh4: ghc randomly segfaults on qemu-sh4-static + +Hello! + +I am currently in the process of bootstrapping ghc for the Debian sh4 port and ran into a strange problem with qemu-sh4-static which randomly segfaults when running ghc to compile a Haskell source: + +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ls +Main.hi Main.hs Setup.hs ghc-pwd.cabal ghc.mk +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +[1 of 1] Compiling Main ( Main.hs, Main.o ) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +[1 of 1] Compiling Main ( Main.hs, Main.o ) +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +[1 of 1] Compiling Main ( Main.hs, Main.o ) +Bad interface file: /usr/local/lib/sh4-unknown-linux-gnu-ghc-7.10.3/time/dist-install/build/Data/Time/Format/Parse.hi + ghc: panic! (the 'impossible' happened) + (GHC version 7.10.3 for sh4-unknown-linux): + getSymtabName:unknown known-key unique +<<details unavailable>> + +Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug + +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +[1 of 1] Compiling Main ( Main.hs, Main.o ) +Linking Main ... +root@jessie32:~/ghc-7.8.4/utils/ghc-pwd# + +As seen above, compiling a Haskell source code often results in a segfault but simply by retrying to run ghc over and over again, the compile process will eventually succeed and no segfault occurs. + +I have created a tarball which contains the sh4 chroot from the example above which also includes ghc, gcc and the source code in question (in /root/ghc-7.8.4/utils/ghc-pwd). To test, it's probably a good idea to replace the qemu-sh4-static binary in /usr/bin with a current git snapshot (which I tried but didn't help). + +> http://users.physik.fu-berlin.de/~glaubitz/sid-sh4-sbuild-ghc.tgz + +In case anyone wants to try ghc with their own sh4 chroot, here's my version of ghc: + +> https://people.debian.org/~glaubitz/sh4-unknown-linux-gnu-ghc-7.10.3.tar.gz + +Just extract in the chroot of the sh4 chroot. + +Please note, that it might be advisable on sh4 to apply the patches from these two bug reports as otherwise qemu-sh4-static won't work properly on sh4 and misses syscall 186: + +> https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/1254824 +> https://bugs.launchpad.net/qemu/+bug/1516408 + +The above issue is reproducible with the two patches applied and without. It's also reproducible with both libc6 2.19 and 2.21 in the chroot. Thus, I am currently out of ideas what else to test. + +Cheers, +Adrian + +Thank you for the 611 MB tar.... + +The behavior is a little bit different on my system: + +root@Quad:~# ls +ghc-7.8.4 ghc_7.8.4-9~bpo8+1.dsc +ghc_7.8.4-9~bpo8+1.debian.tar.xz ghc_7.8.4.orig.tar.xz +root@Quad:~# cd ghc-7.8.4/utils/ghc-p +ghc-pkg/ ghc-pwd/ +root@Quad:~# cd ghc-7.8.4/utils/ghc-p +ghc-pkg/ ghc-pwd/ +root@Quad:~# cd ghc-7.8.4/utils/ghc-pwd/ +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ls +Main Main.hi Main.hs Main.o Setup.hs ghc-pwd.cabal ghc.mk +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main +Main Main.hi Main.hs Main.o +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +root@Quad:~/ghc-7.8.4/utils/ghc-pwd# ghc Main.hs +ghc: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. +qemu: uncaught target signal 6 (Aborted) - core dumped +Aborted (core dumped) + +The emulated "tas.b" instruction is not atomic, this is why sometimes the locking fails... + + +Interestingly, cmake also seems to crash in a similar way: + +- Log: https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng&arch=sh4&ver=0.8.8-1&stamp=1450985460 +- Log: https://buildd.debian.org/status/fetch.php?pkg=texworks&arch=sh4&ver=0.5~svn1363-6%2Bb1&stamp=1450992669 +- Log: https://buildd.debian.org/status/fetch.php?pkg=x265&arch=sh4&ver=1.8-6&stamp=1450995672 +- Log: https://buildd.debian.org/status/fetch.php?pkg=libwebsockets&arch=sh4&ver=1.6.0-2&stamp=1450997039 + +Maybe those are related? + +Just tested with the latest git snapshot of qemu, still no improvement: + +... +checking for gfind... no +checking for find... /usr/bin/find +checking for sort... /usr/bin/sort +checking for GHC Git commit id... given 4986837f8168cacf95c24fecc84d7b36c47f3c11 +checking version of ghc... 8.0.1 +ghc: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. +qemu: uncaught target signal 6 (Aborted) - core dumped +ghc: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. +qemu: uncaught target signal 6 (Aborted) - core dumped +ghc: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. +qemu: uncaught target signal 6 (Aborted) - core dumped +Bootstrapping GHC is a cross compiler. This probably isn't going to work +checking build system type... sh4-unknown-linux-gnu +checking host system type... sh4-unknown-linux-gnu +checking target system type... sh4-unknown-linux-gnu +Build platform inferred as: sh4-unknown-linux +Host platform inferred as: sh4-unknown-linux +Target platform inferred as: sh4-unknown-linux +GHC build : sh4-unknown-linux +GHC host : sh4-unknown-linux +GHC target : sh4-unknown-linux +configure: Building in-tree ghc-pwd +(hangs here) + +The QEMU project is currently considering to move its bug tracking to +another system. For this we need to know which bugs are still valid +and which could be closed already. Thus we are setting older bugs to +"Incomplete" now. + +If you still think this bug report here is valid, then please switch +the state back to "New" within the next 60 days, otherwise this report +will be marked as "Expired". Or please mark it as "Fix Released" if +the problem has been solved with a newer version of QEMU already. + +Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + |