: m ( b p o ^ ] Z disassemble * Changed commands ". file, use "tsave ", and to use it, do "target tfile tracing run at the moment that it was saved. To create a trace collected in them, and use tstatus to display the state of the corefiles. You can select trace frames, print data that was then use that file as a target, similarly to you can do with GDB now has the ability to save the trace buffer into a file, and ** Trace files connection is lost unexpectedly. tell the target agent whether to continue running a trace if the is going. In addition, a new variable disconnected-tracing lets you a trace experiment, then reconnect later to see how the experiment It is now possible to detach GDB from the target while it is running ** Disconnected tracing the regular trace command. fast tracepoint, use the "ftrace" command, with syntax identical to instruction to be replaced is shorter than the jump. To request a might not allow fast tracepoint installation, for instance if the tradeoff is that some program locations on some target architectures speedup can be by two orders of magnitude or more, although the into the target agent rather than a trap instruction. The resulting targets may implement more efficiently, such as by installing a jump GDB now includes an option for defining fast tracepoints, which ** Fast tracepoints Variables" in the manual for more detail. command to create, and "info tvariables" to view; see "Trace State tracepoint actions and condition expressions. Use the "tvariable" $-syntax of GDB convenience variables, and can appear in both count reaches a particular value. Trace state variables share the and then a second tracepoint has a condition that is true when the other, so for instance one tracepoint can count hits in a variable, experiment. They are useful for tracepoints that trigger each are variables managed by the target agent during a tracing GDB tracepoints now include support for trace state variables, which ** Trace state variables GDB's tracepoint facility now includes several new features: * New tracing features already. See also "New commands" and "New options" below. lists inferiors that are not running yet or that have exited in the multi-inferior support. For example, "info inferiors" now manual for more information. This implied some user visible changes session. See "Debugging Multiple Inferiors and Programs" in the simultaneously each running a different program under the same GDB multi-exec) debugging. This allows for debugging multiple inferiors GDB now has support for multi-program (a.k.a. multi-executable or * Multi-program debugging. Renesas RX rx Xilinx MicroBlaze microblaze * New Simulators Renesas RX rx-*-elf Xilinx MicroBlaze microblaze-*-* * New targets and reinterpret_cast<> are now handled by the C++ expression parser. The C++ cast operators static_cast<>, dynamic_cast<>, const_cast<>, ** Cast Operators qualified name. fixed. It is now possible to call overloaded static methods using a All known bugs relating to the printing of virtual base class were ** Bug Fixes print variables using the alias (e.g. (gdb) print C::x). aliased in the current scope (e.g. namepace C=A; ) the user can namepace aliasing has also been added. So, if a namespace is user to inspect variables from imported namespaces. Support for GDB now supports importing of namespaces in C++. This enables the ** Namespace Support * C++ Improvements *** Changes in GDB 7.1 (Organized release by release) What has changed in GDB? ad Q A o 3
G
F
| 7 m l / .
|
: m ( b p o ^ ] Z disassemble * Changed commands ". file, use "tsave ", and to use it, do "target tfile tracing run at the moment that it was saved. To create a trace collected in them, and use tstatus to display the state of the corefiles. You can select trace frames, print data that was then use that file as a target, similarly to you can do with GDB now has the ability to save the trace buffer into a file, and ** Trace files connection is lost unexpectedly. tell the target agent whether to continue running a trace if the is going. In addition, a new variable disconnected-tracing lets you a trace experiment, then reconnect later to see how the experiment It is now possible to detach GDB from the target while it is running ** Disconnected tracing the regular trace command. fast tracepoint, use the "ftrace" command, with syntax identical to instruction to be replaced is shorter than the jump. To request a might not allow fast tracepoint installation, for instance if the tradeoff is that some program locations on some target architectures speedup can be by two orders of magnitude or more, although the into the target agent rather than a trap instruction. The resulting targets may implement more efficiently, such as by installing a jump GDB now includes an option for defining fast tracepoints, which ** Fast tracepoints Variables" in the manual for more detail. command to create, and "info tvariables" to view; see "Trace State tracepoint actions and condition expressions. Use the "tvariable" $-syntax of GDB convenience variables, and can appear in both count reaches a particular value. Trace state variables share the and then a second tracepoint has a condition that is true when the other, so for instance one tracepoint can count hits in a variable, experiment. They are useful for tracepoints that trigger each are variables managed by the target agent during a tracing GDB tracepoints now include support for trace state variables, which ** Trace state variables GDB's tracepoint facility now includes several new features: * New tracing features already. See also "New commands" and "New options" below. lists inferiors that are not running yet or that have exited in the multi-inferior support. For example, "info inferiors" now manual for more information. This implied some user visible changes session. See "Debugging Multiple Inferiors and Programs" in the simultaneously each running a different program under the same GDB multi-exec) debugging. This allows for debugging multiple inferiors GDB now has support for multi-program (a.k.a. multi-executable or * Multi-program debugging. Renesas RX rx Xilinx MicroBlaze microblaze * New Simulators Renesas RX rx-*-elf Xilinx MicroBlaze microblaze-*-* * New targets and reinterpret_cast<> are now handled by the C++ expression parser. The C++ cast operators static_cast<>, dynamic_cast<>, const_cast<>, ** Cast Operators qualified name. fixed. It is now possible to call overloaded static methods using a All known bugs relating to the printing of virtual base class were ** Bug Fixes print variables using the alias (e.g. (gdb) print C::x). aliased in the current scope (e.g. namepace C=A; ) the user can namepace aliasing has also been added. So, if a namespace is user to inspect variables from imported namespaces. Support for GDB now supports importing of namespaces in C++. This enables the ** Namespace Support * C++ Improvements *** Changes in GDB 7.1 (Organized release by release) What has changed in GDB? ad Q A o 3
G
F
| 7 m l / .
|
