X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;ds=inline;f=gdb%2FNEWS;h=741813f4ad6e0416786ea5473ef058204a0442c3;hb=4034d0ff52b0f346efedd2d335ccbc672466da45;hp=7bf1e1acdef7d335a05d6326fbf498f7826a42d1;hpb=9920b4348edbdd83e3f91c85d7174cb92bba204d;p=deliverable%2Fbinutils-gdb.git diff --git a/gdb/NEWS b/gdb/NEWS index 7bf1e1acde..741813f4ad 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -1,7 +1,49 @@ What has changed in GDB? (Organized release by release) -*** Changes since GDB 7.11 +*** Changes since GDB 7.12 + +* GDB and GDBserver now require building with a C++ compiler. + + It is no longer possible to build GDB or GDBserver with a C + compiler. The --disable-build-with-cxx configure option has been + removed. + +* Support for thread names on MS-Windows. + + GDB now catches and handles the special exception that programs + running on MS-Windows use to assign names to threads in the + debugger. + +* New targets + +Synopsys ARC arc*-*-elf32 + +*** Changes in GDB 7.12 + +* GDB and GDBserver now build with a C++ compiler by default. + + The --enable-build-with-cxx configure option is now enabled by + default. One must now explicitly configure with + --disable-build-with-cxx in order to build with a C compiler. This + option will be removed in a future release. + +* GDBserver now supports recording btrace without maintaining an active + GDB connection. + +* GDB now supports a negative repeat count in the 'x' command to examine + memory backward from the given address. For example: + + (gdb) bt + #0 Func1 (n=42, p=0x40061c "hogehoge") at main.cpp:4 + #1 0x400580 in main (argc=1, argv=0x7fffffffe5c8) at main.cpp:8 + (gdb) x/-5i 0x0000000000400580 + 0x40056a : mov %edi,-0x4(%rbp) + 0x40056d : mov %rsi,-0x10(%rbp) + 0x400571 : mov $0x40061c,%esi + 0x400576 : mov $0x2a,%edi + 0x40057b : + callq 0x400536 * Fortran: Support structures with fields of dynamic types and arrays of dynamic types. @@ -27,6 +69,30 @@ Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3] 0x0000000000400d7c in upper () at i386-mpx-sigsegv.c:68 +* Rust language support. + GDB now supports debugging programs written in the Rust programming + language. See https://www.rust-lang.org/ for more information about + Rust. + +* Support for running interpreters on specified input/output devices + + GDB now supports a new mechanism that allows frontends to provide + fully featured GDB console views, as a better alternative to + building such views on top of the "-interpreter-exec console" + command. See the new "new-ui" command below. With that command, + frontends can now start GDB in the traditional command-line mode + running in an embedded terminal emulator widget, and create a + separate MI interpreter running on a specified i/o device. In this + way, GDB handles line editing, history, tab completion, etc. in the + console all by itself, and the GUI uses the separate MI interpreter + for its own control and synchronization, invisible to the command + line. + +* The "catch syscall" command catches groups of related syscalls. + + The "catch syscall" command now supports catching a group of related + syscalls using the 'group:' or 'g:' prefix. + * New commands skip -file file @@ -40,6 +106,28 @@ skip -rfunction regular-expression maint info line-table REGEXP Display the contents of GDB's internal line table data struture. +maint selftest + Run any GDB unit tests that were compiled in. + +new-ui INTERP TTY + Start a new user interface instance running INTERP as interpreter, + using the TTY file for input/output. + +* Python Scripting + + ** gdb.Breakpoint objects have a new attribute "pending", which + indicates whether the breakpoint is pending. + ** Three new breakpoint-related events have been added: + gdb.breakpoint_created, gdb.breakpoint_modified, and + gdb.breakpoint_deleted. + +signal-event EVENTID + Signal ("set") the given MS-Windows event object. This is used in + conjunction with the Windows JIT debugging (AeDebug) support, where + the OS suspends a crashing process until a debugger can attach to + it. Resuming the crashing process, in order to debug it, is done by + signalling an event. + * Support for tracepoints and fast tracepoints on s390-linux and s390x-linux was added in GDBserver, including JIT compiling fast tracepoint's conditional expression bytecode into native code. @@ -59,6 +147,19 @@ maint info line-table REGEXP including JIT compiling fast tracepoint's conditional expression bytecode into native code. +* MI async record =record-started now includes the method and format used for + recording. For example: + + =record-started,thread-group="i1",method="btrace",format="bts" + +* MI async record =thread-selected now includes the frame field. For example: + + =thread-selected,id="3",frame={level="0",addr="0x00000000004007c0"} + +* New targets + +Andes NDS32 nds32*-*-elf + *** Changes in GDB 7.11 * GDB now supports debugging kernel-based threads on FreeBSD. @@ -238,15 +339,13 @@ QThreadEvents stop for that same thread. N stop reply - Indicates that there are no resumed threads left in the target (all threads are stopped). The remote stub reports support for this stop reply to GDB's qSupported query. -QCatchSyscalls:1 [;SYSNO]... -QCatchSyscalls:0 - Enable ("QCatchSyscalls:1") or disable ("QCatchSyscalls:0") - catching syscalls from the inferior process. +QCatchSyscalls + Enables/disables catching syscalls from the inferior process. + The remote stub reports support for this packet to GDB's qSupported query. syscall_entry stop reason Indicates that a syscall was just called. @@ -254,10 +353,6 @@ syscall_entry stop reason syscall_return stop reason Indicates that a syscall just returned. -QCatchSyscalls:1 in qSupported - The qSupported packet may now include QCatchSyscalls:1 in the reply - to indicate support for catching syscalls. - * Extended-remote exec events ** GDB now has support for exec events on extended-remote Linux targets.