Emit and handle (custom) `-register-changed` notification This commit adds new (custom) asynchronous notification about register value being changed. Standard GDB does not notify MI clients about register value being changed when debugging (for example, by CLI command `set $rax = 1` or via Python's `Value.assign()`). This caused libgdb's register value cache being out of sync. In the past, this was partially worked around by manually emiting the notification on `GDBRegisterWithValue` APIs, but this did not (and could not) handle the case register was changed from GDB command line. To solve this problem, this commit installs a custom Python event handler that emits new GDB/MI notification - `-register-changed` - whenever a register changes after debugee is stopped. This has been enabled by upstream GDB commit 4825fd "gdb/python: implement support for sending custom MI async notifications" On libgdbs side, complete inferior state is invalidated. In theory, one could carefully invalidate only the changed `GDBRegisterWithValue` but in certain cases this could also change the backtrace (for example, if one updates stack pointer) or position in code. So it seems safer to just invalidate everything.

     1

@REM -------

     2

@REM make using mingw gnu compiler

     3

@REM type mingwmake, and wait...

     4

@REM do not edit - automatically generated from ProjectDefinition

     5

@REM -------

     6

@SET DEFINES=

     7

@REM Kludge got Mercurial, cannot be implemented in Borland make

     8

@FOR /F "tokens=*" %%i in ('hg root') do SET HGROOT=%%i

     9

@IF "%HGROOT%" NEQ "" SET DEFINES=%DEFINES% "-DHGROOT=%HGROOT%"

    10

    11

@pushd ..\..\stx\rules

    12

@call find_mingw.bat

    13

@popd

    14

make.exe -N -f bc.mak %DEFINES% %USEMINGW_ARG% %*

    15

    16

    17

    18