add 18th iteration of classifier

1 files changed, 53 insertions, 0 deletions

diff --git a/results/classifier/118/graphic/2059 b/results/classifier/118/graphic/2059
new file mode 100644
index 000000000..17ceceba6
--- /dev/null
+++ b/results/classifier/118/graphic/2059
@@ -0,0 +1,53 @@
+graphic: 0.838
+kernel: 0.809
+architecture: 0.727
+device: 0.655
+debug: 0.615
+semantic: 0.608
+ppc: 0.558
+files: 0.556
+performance: 0.535
+PID: 0.508
+hypervisor: 0.480
+vnc: 0.455
+virtual: 0.383
+socket: 0.377
+permissions: 0.371
+x86: 0.364
+user-level: 0.332
+risc-v: 0.332
+TCG: 0.324
+arm: 0.312
+boot: 0.307
+register: 0.299
+peripherals: 0.297
+network: 0.289
+mistranslation: 0.276
+VMM: 0.272
+i386: 0.249
+KVM: 0.203
+assembly: 0.189
+
+Solaris 2.6.5 panic when trying to debug a binary with Sun Workshop V5n1, or V6n1 debugger
+Description of problem:
+Following [this guide](https://www.gekk.info/articles/solaris26.htm), and similarly to issue #1166, the guest panics when one tries to debug a binary with the debugger provided in [Sun Workshop V5n1](https://archive.org/details/sunworkshopforsolaris2vol5num1_704546810revb), and in [Sun Workshop v6n1](https://archive.org/details/devpro_v6n1) as well.
+The Sun Workshop is EOL, available at the archive, with free non-expiring demo licenses [made available](https://archive.org/details/suncomp-lic) by Sun before the Oracle acquisition.
+The guest was patched with the latest available patches included [in this cluster](https://archive.org/details/sun26gnu).
+The following information was collected when debugging bunzip2, but any binary panics the guest.
+```
+panic: Non-parity synchronous error: ctx=54 va=ef7cbc44 pa=e0a8c44
+syncing filesystems... 15 done
+NOTICE: zs3:ring buffer overflow
+```
+Steps to reproduce:
+1. Start the Sun Workshop (SUNWspro/bin/workshop), go to the Debugger in the menu
+2. Debug/New Program, load any binary, place a breakpoint in main or wherever
+3. Execute, guest kernel panic
+Additional information:
+This happens with the Fujitsu MB86904 specified as CPU, and without specifying a cpu, using the default for the SS-5.
+
+![sol26](/uploads/375b25f8614a49bfe634c71520890b5c/sol26.png)
+
+Explicitly setting the TI MicroSparc I and setting memory to 32M seems to start the debugger, the guest still panics, but a bit further down the line
+
+![sol262](/uploads/7a9c834f66fea1706ef92eb65ce8fe39/sol262.png)