summary refs log tree commit diff stats
path: root/results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/1889411
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/1889411')
-rw-r--r--results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/18894113
1 files changed, 3 insertions, 0 deletions
diff --git a/results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/1889411 b/results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/1889411
new file mode 100644
index 00000000..435739f2
--- /dev/null
+++ b/results/classifier/no-thinking-deepseek-r1:70b/reasoning/runtime/1889411
@@ -0,0 +1,3 @@
+The issue describes a problem where GDB cannot unwind the stack when certain signals (like SIGABRT) are triggered while debugging a RISC-V program using QEMU. This appears to be related to how QEMU handles signal delivery and stack unwinding during runtime, rather than a specific instruction or syscall error.
+
+runtime
\ No newline at end of file