summaryrefslogtreecommitdiffstats
path: root/results/scraper/launchpad-without-comments/1318281
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1318281
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloademulator-bug-study-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
emulator-bug-study-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1318281')
-rw-r--r--results/scraper/launchpad-without-comments/131828134
1 files changed, 34 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1318281 b/results/scraper/launchpad-without-comments/1318281
new file mode 100644
index 00000000..1b7170a6
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1318281
@@ -0,0 +1,34 @@
+linux-user: x86_64 target fails to call sys_futex()
+
+I'm building the latest QEMU (06b4f00d53637f2c16a62c2cbaa30bffb045cf88) on ARM to run some x86_64 executables in user mode. This is my configuration:
+
+./configure \
+ --prefix=/root/qemu-x86_64 \
+ --target-list=x86_64-linux-user \
+ --disable-system \
+ --disable-tools
+
+The following program is used for testing:
+
+https://gist.github.com/hujiajie/e8cff43b574b399c8f59#file-test-c
+
+I compile the test program in Debian-7.5-amd64 like this:
+
+gcc -o test `pkg-config --cflags glib-2.0` test.c `pkg-config --static --libs glib-2.0` -static
+
+and launch the program on ARM with
+
+qemu-x86_64 test
+
+The test crashes with the following message:
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault
+
+The output of `strace qemu-x86_64 test` is here:
+
+https://gist.github.com/hujiajie/88d1d5e580d432d11b2d#file-test-strace-log
+
+It seems that the error is caused by the failure of the futex syscall.
+
+qemu-i386 could launch the 32-bit test perfectly, the problem only happens on a x86_64 target. \ No newline at end of file