diff options
| -rw-r--r-- | hurd/running/chroot.mdwn | 1 | ||||
| -rw-r--r-- | microkernel/mach/gnumach/debugging.mdwn | 5 |
2 files changed, 5 insertions, 1 deletions
diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index 67e030cd..699f05a1 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -44,3 +44,4 @@ programs inside the chroot need to be able to access them: # settrans -kp chroot/dev /hurd/firmlink /dev # settrans chroot/tmp /hurd/firmlink /tmp # settrans -c chroot/var/lib/dbus /hurd/firmlink /var/lib/dbus + # settrans -c chroot/run/dbus /hurd/firmlink /run/dbus diff --git a/microkernel/mach/gnumach/debugging.mdwn b/microkernel/mach/gnumach/debugging.mdwn index cf02471d..c5c592b7 100644 --- a/microkernel/mach/gnumach/debugging.mdwn +++ b/microkernel/mach/gnumach/debugging.mdwn @@ -65,9 +65,12 @@ Another interesting feature is watching a variable, by using watch 0x123400 -and then type continue, to let Mach continue execution. The debugger will be entered again on any change in that variable. The watch is implemented in hardware, so it does not disturb or slow down execution at all. +and then type continue, to let Mach continue execution. The debugger will be entered again on any change in that variable. The watch is implemented in hardware, so it does not disturb or slow down execution at all. The same can be achieved programmatically, e.g. using + struct db_watchpoint watch = { .task = NULL, .loaddr= 0x40e, .hiaddr = 0x40e+2, .link = NULL}; + db_set_hw_watchpoint(&watch, 0); + # GDB in QEMU When you're [[running_a_system_in_QEMU|hurd/running/qemu]] you can directly |