diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
| commit | 3e4c5a6261770bced301b5e74233e7866166ea5b (patch) | |
| tree | 9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_i386/host_missing/accel_missing/1135 | |
| parent | e5634e2806195bee44407853c4bf8776f7abfa4f (diff) | |
| download | qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip | |
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_missing/1135')
| -rw-r--r-- | gitlab/issues_text/target_i386/host_missing/accel_missing/1135 | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_missing/1135 b/gitlab/issues_text/target_i386/host_missing/accel_missing/1135 deleted file mode 100644 index 0f5ea8bf3..000000000 --- a/gitlab/issues_text/target_i386/host_missing/accel_missing/1135 +++ /dev/null @@ -1,12 +0,0 @@ -Multiboot: invalid multiboot information block -Description of problem: -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. -Steps to reproduce: - -Additional information: -multiboot: [multiboot](/uploads/55fdfcf30ada0af2d00badf11fcd308c/multiboot) - -toop: [toop](/uploads/de3b63ae021303c544105ba1498f3373/toop) |