Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: gdb-patches@sourceware.cygnus.com
Subject: [RFA] Update NEWS for v5.1
Date: Thu, 19 Jul 2001 09:20:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010719191807.3894A-100000@is> (raw)

Here's my contribution to NEWS updating initiative.  I put there changes 
that invade other maintainers' realms, so please proofread for accuracy.

(Andrew, I'd suggest in the future to request any significant change to 
be accompanied by a NEWS entry, to avoid the pre-release frenzy.)

--- gdb/NEWS.~0	Sun Jul 15 12:24:18 2001
+++ gdb/NEWS	Thu Jul 19 19:12:04 2001
@@ -3,22 +3,18 @@
 
 *** Changes since GDB 5.0:
 
-* "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
-
-* The MI enabled.
-
-The new machine oriented interface (MI) introduced in GDB 5.0 has been
-revised and enabled.
-
 * New native configurations
 
 Alpha FreeBSD					alpha*-*-freebsd*
 x86 FreeBSD 3.x and 4.x				i[3456]86*-freebsd[34]*
 MIPS Linux					mips*-*-linux*
+MIPS SGI Irix 6.x				mips*-sgi-irix6*
+ia64 AIX					ia64-*-aix*
 
 * New targets
 
 Motorola 68HC11 and 68HC12			m68hc11-elf
+UltraSparc running Linux			sparc64-*-linux*
 
 * OBSOLETE configurations and files
 
@@ -54,12 +50,112 @@
 Tahoe						tahoe-*-*
 ser-ocd.c					*-*-*
 
+* GDB requires an ISO C compiler.
+
+Building GDB requires an ISO C compliant compiler.  In particular, the
+sources are fully protoized, and rely on standard headers being
+present.
+
 * Other news:
 
-* All MIPS configurations are multi-arched.
+* "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
+
+* The MI enabled by default.
+
+The new machine oriented interface (MI) introduced in GDB 5.0 has been
+revised and enabled by default.  Packages which use GDB as a debugging
+engine behind a UI or another front end are encouraged to switch to
+using the GDB/MI interface, instead of the old annotations interface
+which is now deprecated.
+
+* Limited support for debugging Pascal programs.
+
+This is pretty much minimal, and many important features are not yet
+supported.  A partial list of problems:
+
+    - Pascal string operations are not supported at all.
+
+    - There are some problems with boolean types.
+
+    - Pascal type hexadecimal constants are not supported
+      because they conflict with the internal variables format.
+
+* Changes in completion.
+
+Commands such as `shell', `run' and `set args', which pass arguments
+to inferior programs, now complete on file names, similar to what
+users expect at the shell prompt.
+
+Commands which accept locations, such as `disassemble', `print',
+`breakpoint', `until', etc. now complete on filenames as well as
+program symbols.  Thus, if you type "break foob TAB", and the source
+files linked into the programs include `foobar.c', that file name will
+be one of the candidates for completion.  However, file names are not
+considered for completion after you typed a colon that delimits a file
+name from a name of a function in that file, as in "break foo.c:bar".
+
+`set demangle-style' completes on available demangling styles.
+
+* New platform-independent commands:
+
+It is now possible to define a post-hook for a command as well as a
+hook that runs before the command.  For more details, see the
+documentation of `hookpost' in the GDB manual.
+
+* Changes in GNU/Linux native debugging.
+
+Attach/detach is supported for multi-threaded programs.
+
+Support for SSE registers was added.
+
+* Changes in MIPS configurations.
 
 Multi-arch support is enabled for all MIPS configurations.
 
+GDB can now be built as native debugger on SGI Irix 6.x systems for
+debugging n32 executables.  (Debugging 64-bit executables is not yet
+supported.)
+
+* Unified support for hardware watchpoints in all x86 configurations.
+
+Most (if not all) native x86 configurations support hardware-assisted
+breakpoints and watchpoints in a unified manner.  This support
+implements debug register sharing between watchpoints, which allows to
+put a virtually infinite number of watchpoints on the same address,
+and also supports watching regions up to 16 bytes with several debug
+registers.
+
+The new maintenance command `maintenance show-debug-regs' toggles
+debugging print-outs in functions that insert, remove, and test
+watchpoints and hardware breakpoints.
+
+* Changes in the DJGPP native configuration.
+
+New command ``info dos sysinfo'' displays assorted information about
+the CPU, OS, memory, and DPMI server.
+
+New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
+display information about segment descriptors stored in GDT, LDT, and
+IDT.
+
+GDB can now pass command lines longer than 126 characters to the
+program being debugged (requires an update to the libdbg.a library
+which is part of the DJGPP development kit).
+
+DWARF2 debug info is now supported.
+
+* Changes in documentation.
+
+The "GDB Internals" manual now has an index.  It also includes
+documentation of `ui_out' functions, GDB coding standards, x86
+hardware watchpoints, and memory region attributes.
+
+Tracepoints-related commands are now fully documented in the GDB
+manual.
+
+All GDB documentation was converted to GFDL, the GNU Free
+Documentation License.
+
 * GDB's version number moved to ``version.in''
 
 The Makefile variable VERSION has been replaced by the file


             reply	other threads:[~2001-07-19  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19  9:20 Eli Zaretskii [this message]
2001-07-19 10:28 ` Andrew Cagney
2001-07-20  1:52 ` Pierre Muller
2001-07-20  3:50   ` Eli Zaretskii
2001-07-20  4:20 ` Pierre Muller
2001-07-20  7:11   ` Eli Zaretskii
2001-07-20 16:12   ` Andrew Cagney
     [not found] <Pine.SUN.3.91.1010722133856.6415A-100000@is>
2001-07-23 12:39 ` Andrew Cagney
2001-07-25  7:47   ` Eli Zaretskii
2001-07-25  8:12     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SUN.3.91.1010719191807.3894A-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox