Public bug reported:
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 subsequentlycauses a segfault in memcpy.
I have a fix for this - just need to educate myself on how to submit a
patch.
** Affects: qemu
Importance: Undecided
Status: New
** Description changed:
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 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 subsequentlycauses a segfault in memcpy.
I have a fix for this - just need to educate myself on how to submit a
patch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869497
Title:
x86_cpu_gdb_read_register segfaults when gdb requests registers
Status in QEMU:
New
Bug description:
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 subsequentlycauses a segfault in memcpy.
I have a fix for this - just need to educate myself on how to submit a
patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869497/+subscriptions
