diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_i386/host_missing/accel_missing/1135 | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip | |
gitlab scraper: download in toml and text format
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, 12 insertions, 0 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 new file mode 100644 index 000000000..0f5ea8bf3 --- /dev/null +++ b/gitlab/issues_text/target_i386/host_missing/accel_missing/1135 @@ -0,0 +1,12 @@ +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) |