diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/boot/1135 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/boot/1135')
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1135 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/boot/1135 b/results/classifier/gemma3:12b/boot/1135 new file mode 100644 index 000000000..1135ea608 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1135 @@ -0,0 +1,13 @@ + +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) |