7 Commits

Author	SHA1	Message	Date
Christian Prochaska	445ecba9b5	monitor_gdb.run: disable pagination earlier ... Issue #5047	2023-11-28 14:24:24 +01:00
Christian Prochaska	471e61f0e4	monitor: move monitor_gdb test commands to separate file ... Fixes #5013	2023-10-04 13:22:08 +02:00
Christian Prochaska	d77cb2b1fc	monitor: add 'qXfer:memory-map:read' command` ... Fixes #5004	2023-10-04 13:22:06 +02:00
Christian Prochaska	7000fb8642	monitor: add more debugging features ... Fixes #4977	2023-08-23 13:46:37 +02:00
Christian Prochaska	02209e5455	monitor: add memory write support ... Fixes #4947	2023-07-14 12:06:32 +02:00
Christian Prochaska	2dd1365af3	monitor: separate 'monitor_gdb' run scripts ... Fixes #4944	2023-07-14 12:06:31 +02:00
Norman Feske	6a57683e52	New debug monitor ... The new monitor component at os/src/monitor is the designated successor of the gdb_monitor. This initial version, however, implements only the subset needed to inspect the memory of the monitored component(s). In contrast to the gdb_monitor, the new component supports the monitoring of multiple components, leveraging the sandbox API. It can therefore be used as a drop-in replacement for the init component. Like the gdb_monitor, the new monitor speaks the GDB protocol over Genode's terminal session. But the protocol implementation does not re-use any gdbserver code, sidestepping the complexities of POSIX. There exist two run scripts illustrating the new component. The os/run/monitor.run script exercises memory inspection via the 'm' command by letting a test program monitor itself. The os/run/monitor_gdb.run script allows for the interactive use of GDB to interact with monitored components. Issue #4917	2023-06-16 11:24:26 +02:00