diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-07 17:18:14 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-07 17:18:14 +0000 |
| commit | 61361f925d4914a6608a0076e64cc2399311ed5f (patch) | |
| tree | 6f717c2ff0b11d7493e60da9757818d119cfb541 /results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909 | |
| parent | 238ec2b7cc1557d6f34c33cc482e4d0cd3e266dd (diff) | |
| download | qemu-analysis-61361f925d4914a6608a0076e64cc2399311ed5f.tar.gz qemu-analysis-61361f925d4914a6608a0076e64cc2399311ed5f.zip | |
add new results
Diffstat (limited to 'results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909')
| -rw-r--r-- | results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909 | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909 b/results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909 new file mode 100644 index 000000000..d1ec63aad --- /dev/null +++ b/results/classifier/no-thinking-deepseek-r1:32b/reasoning/instruction/1909 @@ -0,0 +1,9 @@ +The problem occurs during the execution of a test program under QEMU 8.0.0 when using the `--coverage` option. The segfault is traced to an attempt to increment a gcov counter, specifically at address `0x4fe9d0`, which corresponds to `__llvm_gcov_ctr.5`. The instruction causing the issue is `str x8, [x9, #2512]`, where `$x8` holds the value 1 and `$x9` points to `0x4fe9d0 - 2512 = 0x4fe9d0 - 0x9c0 = 0x4f40d0`. The memory at this address is mapped but appears uninitialized. + +When running the same test program under QEMU 6.2.0, it does not segfault at this point, though a different segfault occurs later due to a bug in the test program itself. + +This issue seems related to how QEMU handles certain memory operations or instructions when coverage instrumentation is enabled. The difference between versions suggests that a change in QEMU's handling of such operations might have introduced the regression. + +Given the context provided, the most likely category for this bug is **instruction** since it involves an instruction execution causing a segfault during program runtime. + +instruction \ No newline at end of file |