blob: 80568f5379eccb39e2f1e9cca7aaee2c34572a3d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify this bug report into one of the given categories. Let's start by reading through the report carefully.
The user mentioned a "heap-buffer-overflow" in the function `sifive_plic_create`. They ran some tests and got an error from Address Sanitizer. The stack trace points to line 463 in `hw/intc/sifive_plic.c`, which is where the overflow occurred.
They also tried modifying the code by changing something to else-if, and that fixed the issue. From this, it seems like there was a logic error leading to an out-of-bounds access or incorrect buffer handling.
Looking at the categories, I see options like "Memory" and others. A heap buffer overflow is clearly a memory-related issue because it involves accessing beyond the allocated memory region. The function `sifive_plic_create` likely allocates some memory, and there's an error in how that memory is being used or accessed.
So, the bug is related to incorrect memory handling, specifically writing past the allocated buffer's end. Therefore, this falls under the "Memory" category.
</think>
The issue described involves a heap buffer overflow, which directly relates to improper memory management. The function `sifive_plic_create` in `hw/intc/sifive_plic.c` accesses memory beyond its allocated bounds.
**Answer:** Memory
|