X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=gdb%2FNEWS;h=dd3da09f02d94450cdf70b17fa69fa5cfc5b886c;hb=9f0500621b6a4908986394eb0fac151ef097f520;hp=d603cf75d14d305902dfe70eee42368b026700ba;hpb=dc304a9424abb58973ffde431264af1deb6abd22;p=deliverable%2Fbinutils-gdb.git diff --git a/gdb/NEWS b/gdb/NEWS index d603cf75d1..dd3da09f02 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -1,7 +1,98 @@ What has changed in GDB? (Organized release by release) -*** Changes since GDB 7.8 +*** Changes since GDB 7.9 + +* The "info source" command now displays the producer string if it was + present in the debug info. This typically includes the compiler version + and may include things like its command line arguments. + +* Python Scripting + + ** gdb.Objfile objects have a new attribute "username", + which is the name of the objfile as specified by the user, + without, for example, resolving symlinks. + +* New options + +* The command 'thread apply all' can now support new option '-ascending' + to call its specified command for all threads in ascending order. + +* Python/Guile scripting + + ** GDB now supports auto-loading of Python/Guile scripts contained in the + special section named `.debug_gdb_scripts'. + +*** Changes in GDB 7.9 + +* GDB now supports hardware watchpoints on x86 GNU Hurd. + +* Python Scripting + + ** You can now access frame registers from Python scripts. + ** New attribute 'producer' for gdb.Symtab objects. + ** gdb.Objfile objects have a new attribute "progspace", + which is the gdb.Progspace object of the containing program space. + ** gdb.Objfile objects have a new attribute "owner". + ** gdb.Objfile objects have a new attribute "build_id", + which is the build ID generated when the file was built. + ** gdb.Objfile objects have a new method "add_separate_debug_file". + ** A new event "gdb.clear_objfiles" has been added, triggered when + selecting a new file to debug. + ** You can now add attributes to gdb.Objfile and gdb.Progspace objects. + ** New function gdb.lookup_objfile. + + New events which are triggered when GDB modifies the state of the + inferior. + + ** gdb.events.inferior_call_pre: Function call is about to be made. + ** gdb.events.inferior_call_post: Function call has just been made. + ** gdb.events.memory_changed: A memory location has been altered. + ** gdb.events.register_changed: A register has been altered. + +* New Python-based convenience functions: + + ** $_caller_is(name [, number_of_frames]) + ** $_caller_matches(regexp [, number_of_frames]) + ** $_any_caller_is(name [, number_of_frames]) + ** $_any_caller_matches(regexp [, number_of_frames]) + +* GDB now supports the compilation and injection of source code into + the inferior. GDB will use GCC 5.0 or higher built with libcc1.so + to compile the source code to object code, and if successful, inject + and execute that code within the current context of the inferior. + Currently the C language is supported. The commands used to + interface with this new feature are: + + compile code [-raw|-r] [--] [source code] + compile file [-raw|-r] filename + +* New commands + +demangle [-l language] [--] name + Demangle "name" in the specified language, or the current language + if elided. This command is renamed from the "maint demangle" command. + The latter is kept as a no-op to avoid "maint demangle" being interpreted + as "maint demangler-warning". + +queue-signal signal-name-or-number + Queue a signal to be delivered to the thread when it is resumed. + +add-auto-load-scripts-directory directory + Add entries to the list of directories from which to load auto-loaded + scripts. + +maint print user-registers + List all currently available "user" registers. + +compile code [-r|-raw] [--] [source code] + Compile, inject, and execute in the inferior the executable object + code produced by compiling the provided source code. + +compile file [-r|-raw] filename + Compile and inject into the inferior the executable object code + produced by compiling the source code stored in the filename + provided. * On resume, GDB now always passes the signal the program had stopped for to the thread the signal was sent to, even if the user changed @@ -14,6 +105,42 @@ confirmation if the program had stopped for a signal and the user switched threads meanwhile. +* "breakpoint always-inserted" modes "off" and "auto" merged. + + Now, when 'breakpoint always-inserted mode' is set to "off", GDB + won't remove breakpoints from the target until all threads stop, + even in non-stop mode. The "auto" mode has been removed, and "off" + is now the default mode. + +* New options + +set debug symbol-lookup +show debug symbol-lookup + Control display of debugging info regarding symbol lookup. + +* MI changes + + ** The -list-thread-groups command outputs an exit-code field for + inferiors that have exited. + +* New targets + +MIPS SDE mips*-sde*-elf* + +* Removed targets + +Support for these obsolete configurations has been removed. + +Alpha running OSF/1 (or Tru64) alpha*-*-osf* +SGI Irix-5.x mips-*-irix5* +SGI Irix-6.x mips-*-irix6* +VAX running (4.2 - 4.3 Reno) BSD vax-*-bsd* +VAX running Ultrix vax-*-ultrix* + +* The "dll-symbols" command, and its two aliases ("add-shared-symbol-files" + and "assf"), have been removed. Use the "sharedlibrary" command, or + its alias "share", instead. + *** Changes in GDB 7.8 * New command line options @@ -86,10 +213,10 @@ show record btrace replay-memory-access maint set target-async (on|off) maint show target-async - This controls whether GDB targets operate in syncronous or - asyncronous mode. Normally the default is asyncronous, if it is + This controls whether GDB targets operate in synchronous or + asynchronous mode. Normally the default is asynchronous, if it is available; but this can be changed to more easily debug problems - occurring only in syncronous mode. + occurring only in synchronous mode. set mi-async (on|off) show mi-async