1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/105/device/1703147 b/results/classifier/105/device/1703147
new file mode 100644
index 000000000..7fb876528
--- /dev/null
+++ b/results/classifier/105/device/1703147
@@ -0,0 +1,73 @@
+device: 0.471
+socket: 0.466
+semantic: 0.316
+network: 0.306
+other: 0.303
+mistranslation: 0.242
+vnc: 0.214
+graphic: 0.177
+boot: 0.177
+assembly: 0.151
+KVM: 0.144
+instruction: 0.098
+
+Xfer:features:read truncating xml sent to gdb frontends
+
+Around line 1326 in gdbstub.c:
+
+            if (len > (MAX_PACKET_LENGTH - 5) / 2)
+                len = (MAX_PACKET_LENGTH - 5) / 2;
+
+is truncating processor reg description xml files longer than 2045 bytes.  Deleting these lines works for my immediate need, but they seem to be trying to fix some buffer overrun condition so I won't offer a patch until we understand their purpose.
+
+On 8 July 2017 at 22:19, Duane Voth <email address hidden> wrote:
+> Around line 1326 in gdbstub.c:
+>
+>             if (len > (MAX_PACKET_LENGTH - 5) / 2)
+>                 len = (MAX_PACKET_LENGTH - 5) / 2;
+>
+> is truncating processor reg description xml files longer than 2045
+> bytes.  Deleting these lines works for my immediate need, but they seem
+> to be trying to fix some buffer overrun condition so I won't offer a
+> patch until we understand their purpose.
+
+Those lines prevent the packet we're constructing overrunning
+the buf[] array (in the worst case the packet encoding could
+use 2 bytes of buffer for every byte of payload). It's probably
+working for you without them because (a) the XML payload doesn't
+come near the worst-case and (b) buf[] is followed on the stack
+by mem_buf[] which happens to be unused here so overrunning into
+it has no visible harmful effects.
+
+Truncating the XML is clearly not what we want though so we
+should do something more intelligent...
+
+thanks
+-- PMM
+
+
+The QEMU project is currently considering to move its bug tracking to
+another system. For this we need to know which bugs are still valid
+and which could be closed already. Thus we are setting older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
+Problematic code now around lines 2221 (in handle_query_xfer_features) ... lol I'm the only one impacted ... all the large register set cpus can be affected.
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/458
+
+