diff options
Diffstat (limited to 'results/classifier/phi4:14b/reasoning/runtime')
46 files changed, 82 insertions, 0 deletions
diff --git a/results/classifier/phi4:14b/reasoning/runtime/1070 b/results/classifier/phi4:14b/reasoning/runtime/1070 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1070 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1086 b/results/classifier/phi4:14b/reasoning/runtime/1086 new file mode 100644 index 000000000..7945a4362 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1086 @@ -0,0 +1,3 @@ +runtime + +The bug report describes issues that arise during the execution of test suites for numpy and scipy when running on QEMU for ppc64le architecture. The problems include array comparisons failing with unexpected results such as garbage values, permutations, or fundamental differences in output. These types of errors typically occur at runtime rather than being caused by a specific faulty instruction or syscall issue. Therefore, the most appropriate classification is "runtime." \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1156313 b/results/classifier/phi4:14b/reasoning/runtime/1156313 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1156313 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/121 b/results/classifier/phi4:14b/reasoning/runtime/121 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/121 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1211 b/results/classifier/phi4:14b/reasoning/runtime/1211 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1211 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/122 b/results/classifier/phi4:14b/reasoning/runtime/122 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/122 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1221966 b/results/classifier/phi4:14b/reasoning/runtime/1221966 new file mode 100644 index 000000000..95da7b51f --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1221966 @@ -0,0 +1,3 @@ +runtime + +The issue described involves a segmentation fault occurring during execution, specifically related to buffer handling (`static_code_gen_buffer`). This indicates an error happening at runtime rather than being tied to any specific instruction or syscall directly mentioned in the report. Segmentation faults are typically associated with accessing memory incorrectly and usually occur during program execution (i.e., runtime). \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1361912 b/results/classifier/phi4:14b/reasoning/runtime/1361912 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1361912 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1457275 b/results/classifier/phi4:14b/reasoning/runtime/1457275 new file mode 100644 index 000000000..75c1975a0 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1457275 @@ -0,0 +1,3 @@ +runtime + +The issue involves QEMU's behavior during execution (the m{,un}map loop) rather than a specific instruction or system call failure. It is related to how memory mapping and unmapping are handled in runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1606 b/results/classifier/phi4:14b/reasoning/runtime/1606 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1606 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1654137 b/results/classifier/phi4:14b/reasoning/runtime/1654137 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1654137 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1697 b/results/classifier/phi4:14b/reasoning/runtime/1697 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1697 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1773743 b/results/classifier/phi4:14b/reasoning/runtime/1773743 new file mode 100644 index 000000000..07f34de24 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1773743 @@ -0,0 +1,3 @@ +runtime + +This classification is appropriate because the issue arises during the execution time when using QEMU and GDB together, specifically involving signal handling (SIGPROF). It doesn't involve incorrect instructions or syscall errors directly but rather an unexpected behavior in how signals are processed at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1793539 b/results/classifier/phi4:14b/reasoning/runtime/1793539 new file mode 100644 index 000000000..741d1d02c --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1793539 @@ -0,0 +1,3 @@ +runtime + +This issue involves QEMU handling CPU signals outside of the virtual CPU context during runtime execution, rather than involving faulty instructions or system calls directly. Therefore, it fits best under "runtime." \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1798 b/results/classifier/phi4:14b/reasoning/runtime/1798 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1798 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1807 b/results/classifier/phi4:14b/reasoning/runtime/1807 new file mode 100644 index 000000000..b8d93257a --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1807 @@ -0,0 +1,3 @@ +runtime + +The issue arises during the execution phase when using `printf` or `puts`, indicating it's related to runtime behavior rather than faulty instructions or syscalls directly. The ELF image being invalid for certain QEMU architectures further suggests a mismatch at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1814128 b/results/classifier/phi4:14b/reasoning/runtime/1814128 new file mode 100644 index 000000000..5af930635 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1814128 @@ -0,0 +1,3 @@ +runtime + +The issue described involves how QEMU handles the brk setting for static PIE binaries during runtime, leading to a segmentation fault due to improper memory layout arrangements. This is not related to faulty instructions or syscall errors but rather concerns how resources are managed at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1840922 b/results/classifier/phi4:14b/reasoning/runtime/1840922 new file mode 100644 index 000000000..199ab91a6 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1840922 @@ -0,0 +1,3 @@ +runtime + +The issue involves an unhandled CPU exception occurring at runtime, likely due to how the code is executed or interacts with QEMU's emulation environment. The problem is not directly related to a specific instruction or syscall but rather occurs during execution (at runtime). \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1854 b/results/classifier/phi4:14b/reasoning/runtime/1854 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1854 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1857 b/results/classifier/phi4:14b/reasoning/runtime/1857 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1857 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/1860056 b/results/classifier/phi4:14b/reasoning/runtime/1860056 new file mode 100644 index 000000000..7f3f1b4ce --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1860056 @@ -0,0 +1,3 @@ +runtime + +The issue appears to be related to running a MIPS binary that segfaults due to some problem specific to big endian 32-bit MIPS architecture when executed using QEMU on a Debian system. This classification fits under "runtime" because it involves an error occurring during execution, not necessarily with a single instruction or syscall but rather with the broader execution environment and compatibility issues at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1886097 b/results/classifier/phi4:14b/reasoning/runtime/1886097 new file mode 100644 index 000000000..20485c5a8 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1886097 @@ -0,0 +1,3 @@ +runtime + +The issue involves discrepancies in how memory boundaries and program breaks are calculated during execution, affecting runtime behavior rather than specific instructions or syscalls directly. The problem arises due to differences between QEMU's handling and Linux's native implementation at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/1952 b/results/classifier/phi4:14b/reasoning/runtime/1952 new file mode 100644 index 000000000..35bb8c3d7 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/1952 @@ -0,0 +1,3 @@ +runtime + +The issue arises from how QEMU's ELF loader processes virtual addresses and offsets for `PT_LOAD` segments during emulation, not due to an instruction or syscall error itself. The problem is related to handling binary segment layouts at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/2027 b/results/classifier/phi4:14b/reasoning/runtime/2027 new file mode 100644 index 000000000..d992e4d3b --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2027 @@ -0,0 +1,3 @@ +runtime + +The issue described involves the Go runtime functions and garbage collector activities (`gcBgMarkWorker`, `gcBgMarkStartWorkers`), as well as system calls like `mmap`. This indicates that the problem lies within the runtime environment rather than a specific instruction or isolated syscall failure. The detailed mention of goroutines related to garbage collection further supports classifying this bug under "runtime". \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/2487 b/results/classifier/phi4:14b/reasoning/runtime/2487 new file mode 100644 index 000000000..d7bd39301 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2487 @@ -0,0 +1,3 @@ +runtime + +The issue arises due to a code path that should not be reached during execution, leading to QEMU crashing. This is characteristic of a runtime error where unexpected conditions or logic lead to failure after program start. The presence of specific commit changes also points towards modifications affecting how instructions are handled at runtime. \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/2505 b/results/classifier/phi4:14b/reasoning/runtime/2505 new file mode 100644 index 000000000..b9aef96e8 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2505 @@ -0,0 +1,3 @@ +runtime + +This bug report describes an issue related to how CPU flags are interpreted during the selection process in QEMU, rather than involving a specific instruction or syscall error. It pertains to behavior that occurs during execution (or "runtime"). \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/2525 b/results/classifier/phi4:14b/reasoning/runtime/2525 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2525 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/2569 b/results/classifier/phi4:14b/reasoning/runtime/2569 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2569 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/2580 b/results/classifier/phi4:14b/reasoning/runtime/2580 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2580 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/2598 b/results/classifier/phi4:14b/reasoning/runtime/2598 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2598 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/261 b/results/classifier/phi4:14b/reasoning/runtime/261 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/261 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/276 b/results/classifier/phi4:14b/reasoning/runtime/276 new file mode 100644 index 000000000..a1c8a0a66 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/276 @@ -0,0 +1,2 @@ +runtime + diff --git a/results/classifier/phi4:14b/reasoning/runtime/280 b/results/classifier/phi4:14b/reasoning/runtime/280 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/280 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/2815 b/results/classifier/phi4:14b/reasoning/runtime/2815 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2815 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/2846 b/results/classifier/phi4:14b/reasoning/runtime/2846 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/2846 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/311 b/results/classifier/phi4:14b/reasoning/runtime/311 new file mode 100644 index 000000000..a1c8a0a66 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/311 @@ -0,0 +1,2 @@ +runtime + diff --git a/results/classifier/phi4:14b/reasoning/runtime/324 b/results/classifier/phi4:14b/reasoning/runtime/324 new file mode 100644 index 000000000..a1c8a0a66 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/324 @@ -0,0 +1,2 @@ +runtime + diff --git a/results/classifier/phi4:14b/reasoning/runtime/326 b/results/classifier/phi4:14b/reasoning/runtime/326 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/326 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/355 b/results/classifier/phi4:14b/reasoning/runtime/355 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/355 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/356 b/results/classifier/phi4:14b/reasoning/runtime/356 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/356 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/419 b/results/classifier/phi4:14b/reasoning/runtime/419 new file mode 100644 index 000000000..a1c8a0a66 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/419 @@ -0,0 +1,2 @@ +runtime + diff --git a/results/classifier/phi4:14b/reasoning/runtime/442 b/results/classifier/phi4:14b/reasoning/runtime/442 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/442 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/616 b/results/classifier/phi4:14b/reasoning/runtime/616 new file mode 100644 index 000000000..8fbb022a9 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/616 @@ -0,0 +1,3 @@ +runtime + +The issue described involves incorrect handling of overflow conditions during execution through QEMU's emulation of s390x architecture, rather than a specific faulty instruction or syscall error. The bug report discusses how condition codes are set, indicating it occurs at runtime when executing compiled code via an emulator. Thus, it falls under the category "runtime." \ No newline at end of file diff --git a/results/classifier/phi4:14b/reasoning/runtime/704 b/results/classifier/phi4:14b/reasoning/runtime/704 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/704 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/817 b/results/classifier/phi4:14b/reasoning/runtime/817 new file mode 100644 index 000000000..3482c3726 --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/817 @@ -0,0 +1 @@ +runtime diff --git a/results/classifier/phi4:14b/reasoning/runtime/922 b/results/classifier/phi4:14b/reasoning/runtime/922 new file mode 100644 index 000000000..2459a4b8c --- /dev/null +++ b/results/classifier/phi4:14b/reasoning/runtime/922 @@ -0,0 +1,3 @@ +runtime + +The issue described involves random segmentation faults occurring during the execution of a program using QEMU to emulate ARM binaries on an x86_64 host. This behavior is consistent with runtime errors, as it happens while the program is running and does not directly involve specific instructions or syscalls themselves being faulty. Instead, it suggests an instability in the execution environment that occurs unpredictably during runtime. \ No newline at end of file |