From 238ec2b7cc1557d6f34c33cc482e4d0cd3e266dd Mon Sep 17 00:00:00 2001
From: Christian Krinitsin <mail@krinitsin.com>
Date: Sun, 6 Jul 2025 16:43:19 +0000
Subject: add results

---
 results/classifier/gemma3:27b/runtime/2123 | 34 ++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 results/classifier/gemma3:27b/runtime/2123

(limited to 'results/classifier/gemma3:27b/runtime/2123')

diff --git a/results/classifier/gemma3:27b/runtime/2123 b/results/classifier/gemma3:27b/runtime/2123
new file mode 100644
index 000000000..ec7f9aaa9
--- /dev/null
+++ b/results/classifier/gemma3:27b/runtime/2123
@@ -0,0 +1,34 @@
+
+
+
+Invalid subprocess commands spawns successfully when running under QEMU
+Description of problem:
+When executing a subprocess from with a non-existing command EQMU still spawns a process.
+
+Consider this small rust program for instance:
+```rust
+use std::process::Command;
+
+fn main() {
+    match Command::new("thisdoesnotexist").spawn() {
+        Ok(child) => {
+            println!("Child process id is {}", child.id());
+        }
+        Err(_) => {
+            println!("This should happen");
+        }
+    }
+}
+```
+
+**Executing with `qemu-aarch64`:**
+```shell
+qemu-aarch64 ./rust-app
+Child process id is 20182
+```
+
+**Executing regularly:**
+```shell
+./rust-app
+This should happen
+```
-- 
cgit 1.4.1