Ryan Fleury 95f4ade10d lift wait-for-process-memory-cache-update out of d_process_write, since that path runs on control thread now too as the general 'process handle write' abstraction - just move into the rd_eval_space_write path, since that wait was only for UI benefit anyways

2026-05-19 14:35:29 -07:00

..

generated

minidump format types; open crash dump command, stub out opening path in control thread; expand d_handles to support machine id, entity id, *and* 'controller kind', which can be either a dump file or a demon - this properly separates the true process control abstraction (demon) from opening a regular dump file on any machine, which will let us trivially support any kind of dump file on any platform; also fix bad cfg tree state leak

2026-05-16 18:26:23 -07:00

dbg_engine_core.c

linux -> prefix user raddbg data with ., so we get ~/.raddbg normally - on windows keep normal style

2026-05-18 20:18:53 -07:00

dbg_engine_core.h

dbg_engine: shift thread register reads / process memory reads -> abstraction layer, rather than directly calling into demon; cache crash dump info, like thread info & memory ranges; implement thread reg reads & memory reads for dumps by using this acceleration structure when we have a dump handle, instead of regular demon reads.

2026-05-18 14:51:17 -07:00

dbg_engine_ctrl.c

lift wait-for-process-memory-cache-update out of d_process_write, since that path runs on control thread now too as the general 'process handle write' abstraction - just move into the rd_eval_space_write path, since that wait was only for UI benefit anyways

2026-05-19 14:35:29 -07:00

dbg_engine_ctrl.h

lift wait-for-process-memory-cache-update out of d_process_write, since that path runs on control thread now too as the general 'process handle write' abstraction - just move into the rd_eval_space_write path, since that wait was only for UI benefit anyways

2026-05-19 14:35:29 -07:00

dbg_engine_inc.c

fold ctrl layer into dbg engine - no benefit to disallowing dependence on debug engine types inside of ctrl, and it has been causing unnecessary barriers for eventual eval magic.

2026-04-22 12:44:18 -07:00

dbg_engine_inc.h

fold ctrl layer into dbg engine - no benefit to disallowing dependence on debug engine types inside of ctrl, and it has been causing unnecessary barriers for eventual eval magic.

2026-04-22 12:44:18 -07:00

dbg_engine_user.c

lift wait-for-process-memory-cache-update out of d_process_write, since that path runs on control thread now too as the general 'process handle write' abstraction - just move into the rd_eval_space_write path, since that wait was only for UI benefit anyways

2026-05-19 14:35:29 -07:00

dbg_engine_user.h

minidump format types; open crash dump command, stub out opening path in control thread; expand d_handles to support machine id, entity id, *and* 'controller kind', which can be either a dump file or a demon - this properly separates the true process control abstraction (demon) from opening a regular dump file on any machine, which will let us trivially support any kind of dump file on any platform; also fix bad cfg tree state leak

2026-05-16 18:26:23 -07:00

dbg_engine.mdesk

checkpoint on dump file parsing / cache construction; temporarily turn off crash dump command, since still wip

2026-05-19 09:56:01 -07:00