summary refs log tree commit diff stats
path: root/gitlab/issues/target_i386/host_missing/accel_missing/1135.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_i386/host_missing/accel_missing/1135.toml')
-rw-r--r--gitlab/issues/target_i386/host_missing/accel_missing/1135.toml20
1 files changed, 20 insertions, 0 deletions
diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/1135.toml b/gitlab/issues/target_i386/host_missing/accel_missing/1135.toml
new file mode 100644
index 000000000..b68a8c9d4
--- /dev/null
+++ b/gitlab/issues/target_i386/host_missing/accel_missing/1135.toml
@@ -0,0 +1,20 @@
+id = 1135
+title = "Multiboot: invalid multiboot information block"
+state = "opened"
+created_at = "2022-08-01T14:09:39.403Z"
+closed_at = "n/a"
+labels = ["target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1135"
+host-os = "Windows 11 with MSYS"
+host-arch = "x86_64"
+qemu-version = "4e06b3fc1b5e1ec03f22190eabe56891dc9c2236"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """Breakpoint at 0x85d4, this is the entrypoint of this Multiboot loader.
+According to the Multiboot specification, the EAX register should be a pointer to the Multiboot information block. When I am testing, it is 0x9500. However, when dumping the memory using `dump binary memory`, nearby memory areas are all zeros.
+
+When dumping some bigger memory aeras, I found that the module hasbeen loaded to the memory successfully, altough MBI was broken."""
+reproduce = """"""
+additional = """multiboot: [multiboot](/uploads/55fdfcf30ada0af2d00badf11fcd308c/multiboot)
+
+toop: [toop](/uploads/de3b63ae021303c544105ba1498f3373/toop)"""