summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1888728
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/1888728
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1888728')
-rw-r--r--results/scraper/launchpad-without-comments/188872819
1 files changed, 19 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1888728 b/results/scraper/launchpad-without-comments/1888728
new file mode 100644
index 000000000..1ebd1a6f8
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1888728
@@ -0,0 +1,19 @@
+Bare chroot in linux-user fails with pgb_reserved_va: Assertion `guest_base != 0' failed.
+
+Trying to run a bare chroot with no additional bind mounts fails on git master (8ffa52c20d5693d454f65f2024a1494edfea65d4) with:
+
+root@nofan:~/qemu> chroot /local_scratch/sid-m68k-sbuild/
+qemu-m68k-static: /root/qemu/linux-user/elfload.c:2315: pgb_reserved_va: Assertion `guest_base != 0' failed.
+Aborted
+root@nofan:~/qemu>
+
+The problem can be worked around by bind-mounting /proc from the host system into the target chroot:
+
+root@nofan:~/qemu> mount -o bind /proc/ /local_scratch/sid-m68k-sbuild/proc/
+root@nofan:~/qemu> chroot /local_scratch/sid-m68k-sbuild/
+bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
+(sid-m68k-sbuild)root@nofan:/#
+
+Host system is an up-to-date Debian unstable (2020-07-23).
+
+I have not been able to bisect the issue yet since there is another annoying linux-user bug (virtual memory exhaustion) that was somewhere introduced and fixed between v5.0.0 and HEAD and overshadows the original Assertion failure bug.
\ No newline at end of file