blob: 5ad3afbefe8276a9305607dc6f9a33b478417216 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to classify this bug report into one of the given categories. Let's see what the problem is.
The user mentioned a segfault in `artist_vram_read`. Segfaults usually mean there's an invalid memory access happening. Looking at the backtrace, the error occurs in `artist.c` at line 1174. The function name suggests it's related to reading from VRAM (Video RAM), which is part of the graphics handling.
The stack trace shows that after `artist_vram_read`, it goes through several memory-related functions like `memory_region_read_accessor`. But the root cause seems to be in how the artist is accessing the VRAM, possibly due to incorrect addressing or invalid memory operations.
Since `artist_vram_read` is part of the display subsystem and handles graphics data, the issue likely falls under the 'graphic' category.
</think>
The bug report involves a segfault occurring in `artist_vram_read`, which is related to accessing VRAM for graphical purposes. This points to an issue with the graphics handling.
Answer: graphic
|