Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2024-11-01 04:11:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
reactos/drivers/base/kdgdb/CMakeLists.txt

29 lines
607 B
CMake
Raw Normal View History

[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
spec2def(kdcom.dll kdgdb.spec ADD_IMPORTLIB)
list(APPEND SOURCE
[CMAKE] * Make the minimum required version 2.8. * Remove redundant psdk dependencies. * Tidy up CMake files. svn path=/trunk/; revision=64795
2014-10-17 23:28:29 +00:00
gdb_input.c
gdb_receive.c
gdb_send.c
[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
kdcom.c
kdpacket.c
[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
2014-09-15 22:05:21 +00:00
utils.c
[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
kdgdb.h)
# TODO: AMD64, ARM...
if(ARCH STREQUAL "i386")
[CMAKE] * Make the minimum required version 2.8. * Remove redundant psdk dependencies. * Tidy up CMake files. svn path=/trunk/; revision=64795
2014-10-17 23:28:29 +00:00
list(APPEND SOURCE i386_sup.c)
[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
endif()
[CMAKE] Use modules instead of shared libraries There is no need to compile our DLLs as shared libraries since we are managing symbols exports and imports through spec files. On my system, this reduces the configure-time by a factor of two.
2019-03-20 13:19:48 +00:00
add_library(kdcom MODULE
[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
${SOURCE}
kdgdb.rc
${CMAKE_CURRENT_BINARY_DIR}/kdcom.def)
Use set_module_type() with module type == "module" instead of specifying that the entrypoint is 0, for resource-only dlls. svn path=/trunk/; revision=72841
2016-09-28 20:21:31 +00:00
set_module_type(kdcom module IMAGEBASE 0x00010000)
[KDGDB] - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together. It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work) To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea. svn path=/trunk/; revision=64121
2014-09-11 20:55:42 +00:00
set_subsystem(kdcom native)
add_importlibs(kdcom ntoskrnl hal)
target_link_libraries(kdcom cportlib)
add_pch(kdcom kdgdb.h SOURCE)
add_cd_file(TARGET kdcom DESTINATION reactos/system32 NO_CAB FOR all)
Reference in a new issue Copy permalink