- update to 3.21.0:
  * When GDB is used to debug a program running under valgrind
    using the valgrind gdbserver, GDB will automatically load some
    python code provided in valgrind defining GDB front end
    commands corresponding to the valgrind monitor commands.
  * These GDB front end commands accept the same format as
    the monitor commands directly sent to the Valgrind
    gdbserver.
    These GDB front end commands provide a better integration
    in the GDB command line interface, so as to use for example
    GDB auto-completion, command specific help, searching for
    a command or command help matching a regexp, ...
    For relevant monitor commands, GDB will evaluate arguments
    to make the use of monitor commands easier.
    For example, instead of having to print the address of a
    variable to pass it to a subsequent monitor command, the
    GDB front end command will evaluate the address argument.
  * The vgdb utility now supports extended-remote protocol when
    invoked with --multi. In this mode the GDB run command is
    supported. Which means you don't need to run gdb and
    valgrind from different terminals.
  * The behaviour of realloc with a size of zero can now
    be changed for tools that intercept malloc. Those
    tools are memcheck, helgrind, drd, massif and dhat.
    Realloc implementations generally do one of two things
       - free the memory like free() and return NULL
         (GNU libc and ptmalloc).
       - either free the memory and then allocate a
         minimum sized block or just return the
         original pointer. Return NULL if the

• Files Changed
• Browse Source