[KDGDB]
authorJérôme Gardou <jerome.gardou@reactos.org>
Mon, 15 Sep 2014 22:05:21 +0000 (22:05 +0000)
committerJérôme Gardou <jerome.gardou@reactos.org>
Mon, 15 Sep 2014 22:05:21 +0000 (22:05 +0000)
commitde914f2aed69dcd0d692b97730c3301495d377a9
tree3d81ff58e0d11610d5c69dde73f64c063196b27d
parent000f2277849f7763331c83575143c72141b38bc3
[KDGDB]
 - As pid and tid 0 have a special meaning in GDB, use off-by-one thread and process ID when communicating with it
 - Properly read registers and memory from foreign thread and processes. (This time it was tested and proved to work reliably. __writecr3 ftw!)
 - Loop the list of processes and threads when trying to find them from ID, as PsLookupProessByThreadId and friends can't be used since we can be at any IRQL.
 - Add a few more debug prints to help diagnosing problems.
CORE-8531

svn path=/trunk/; revision=64166
reactos/drivers/base/kdgdb/CMakeLists.txt
reactos/drivers/base/kdgdb/gdb_input.c
reactos/drivers/base/kdgdb/gdb_send.c
reactos/drivers/base/kdgdb/i386_sup.c
reactos/drivers/base/kdgdb/kdgdb.h
reactos/drivers/base/kdgdb/kdpacket.c
reactos/drivers/base/kdgdb/utils.c [new file with mode: 0644]