summary refs log tree commit diff stats
path: root/results/classifier/118/virtual/1869073
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/virtual/1869073')
-rw-r--r--results/classifier/118/virtual/186907349
1 files changed, 49 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/1869073 b/results/classifier/118/virtual/1869073
new file mode 100644
index 000000000..ae74a1df0
--- /dev/null
+++ b/results/classifier/118/virtual/1869073
@@ -0,0 +1,49 @@
+virtual: 0.966
+graphic: 0.938
+architecture: 0.873
+performance: 0.867
+user-level: 0.858
+device: 0.815
+debug: 0.801
+semantic: 0.764
+arm: 0.725
+PID: 0.711
+hypervisor: 0.698
+mistranslation: 0.667
+register: 0.613
+vnc: 0.609
+permissions: 0.607
+VMM: 0.568
+files: 0.529
+ppc: 0.513
+risc-v: 0.499
+network: 0.483
+boot: 0.470
+socket: 0.457
+TCG: 0.446
+assembly: 0.379
+peripherals: 0.365
+kernel: 0.364
+KVM: 0.317
+i386: 0.231
+x86: 0.228
+
+qemu-arm-static crashes "segmentation fault" when running "git clone -s"
+
+I want to use qemu-arm-static to cross-compile software. The compiler itself is a native cross-compiler connected via "distcc".
+
+The problem is that a script tries to do some stuff with "git" and with a "git clone -s" command the whole story reproducibly stops with a "segmentation fault".
+
+I don't know how to properly debug the issue but it happens 100% of the time that I get the "crash" or git just hangs forever with 100% CPU usage.
+
+What is the version of QEMU you are using?
+
+Actually this one magically went good. I'm testing in Virtual Box as my ARM64 host. Maybe something went wrong there. After rebooting the whole machine today "git" works well.
+
+Will reopen if it happens again...
+
+"git crashes" was a known issue with some older versions of QEMU (we had race conditions and git happens to go multi-threaded for some operations including I think 'clone'), but they should all now be fixed. If it does happen again I would recommend trying the most recent QEMU release.
+
+
+Let's assume that this is fixed. Please open a new bug if it happens again.
+