summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1869497
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1869497
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1869497')
-rw-r--r--results/scraper/launchpad-without-comments/186949710
1 files changed, 10 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1869497 b/results/scraper/launchpad-without-comments/1869497
new file mode 100644
index 000000000..823b58066
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1869497
@@ -0,0 +1,10 @@
+x86_cpu_gdb_read_register segfaults when gdb requests registers
+
+When attempting to attach to the gdbstub, a segfault occurs.
+
+I traced this down to a problem in a call to gdb_get_reg16 where the mem_buf
+was being treated like a uint8_t* instead of a GByteArray.  The buffer passed
+to gdb_get_reg16 ends up passing an invalid GByteArray pointer, which subsequently
+causes a segfault in memcpy.
+
+I have a fix for this - just need to educate myself on how to submit a patch.
\ No newline at end of file