blob: cb3e8351490acd5ebf3450407984511a10c81e40 (
plain) (
blame)
1
2
3
4
5
6
7
|
<think>
Okay, let's see. The user is reporting a bug in QEMU's handling of the ARM semihosting HEAPINFO call. The problem is that QEMU is interpreting the PARAMETER REGISTER incorrectly. According to the ARM spec, the parameter should be a pointer to a four-field data block, but QEMU is treating it as the data block directly. This leads to incorrect memory writes and crashes when using Newlib's semihosting mode.
So, the issue here is about how QEMU processes the semihosting syscall, specifically the HEAPINFO operation. The mistake is in the way the parameter is handled—QEMU is not following the ARM specification correctly. Since semihosting is part of the ARM architecture's syscall interface, this would fall under syscall handling. The problem isn't with the instruction itself (like an incorrect opcode or execution), but rather the system call's parameters and their processing. Therefore, the category should be syscall.
</think>
syscall
|