src-test2/sys/gdb, branch releng/6.3 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=releng%2F6.3 2005-03-28T18:31:18Z check return value of gdb_rx_varhex 2005-03-28T18:31:18Z Sam Leffler sam@FreeBSD.org 2005-03-28T18:31:18Z urn:sha1:4af77ece56c4724c50f9b788c5d83bc2d71042fa Noticed by: Coverity Prevent analysis tool Reviewed by: kan /* -> /*- for copyright notices, minor format tweaks as necessary 2005-01-06T18:27:30Z Warner Losh imp@FreeBSD.org 2005-01-06T18:27:30Z urn:sha1:fa521b036670715f43656cf6c8bebc818f8b06c8 Change gdb_cpu_setreg() to not take the value to which to set the 2004-12-01T06:40:35Z Marcel Moolenaar marcel@FreeBSD.org 2004-12-01T06:40:35Z urn:sha1:bcc5241c43307d18ef4cb61b4f98eb624d31367d specified register, but a pointer to the in-memory representation of that value. The reason for this is twofold: 1. Not all registers can be represented by a register_t. In particular FP registers fall in that category. Passing the new register value by reference instead of by value makes this point moot. 2. When we receive a G or P packet, both are for writing a register, the packet will have the register value in target-byte order and in the memory representation (modulo the fact that bytes are sent as 2 printable hexadecimal numbers of course). We only need to decode the packet to have a pointer to the register value. This change fixes the bug of extracting the register value of the P packet as a hexadecimal number instead of as a bit array. The quick (and dirty) fix to bswap the register value in gdb_cpu_setreg() as it has been added on i386 and amd64 can therefore be removed and has in fact been that. Tested on: alpha, amd64, i386, ia64, sparc64 Comment-out the debugging printf I left in in case there were some 2004-08-10T19:32:33Z Marcel Moolenaar marcel@FreeBSD.org 2004-08-10T19:32:33Z urn:sha1:03e62bf373948673740b4bd65a2e86ecb7182066 packet related problems. No problems have been reported. Introduce the GDB debugger backend for the new KDB framework. The 2004-07-10T17:47:22Z Marcel Moolenaar marcel@FreeBSD.org 2004-07-10T17:47:22Z urn:sha1:72d44f31a6b1f89adcfde641c8ddae288ea3804f backend improves over the old GDB support in the following ways: o Unified implementation with minimal MD code. o A simple interface for devices to register themselves as debug ports, ala consoles. o Compression by using run-length encoding. o Implements GDB threading support.