[patch/commit] News cleanups.

Andrew Cagney
2002-08-04T00:03:58Z

[-- Attachment #1: Type: text/plain, Size: 79 bytes --]

Hello,

I've committed the following cleanups to the NEWS file.

enjoy,
Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1752 bytes --]

2002-08-03 Andrew Cagney <ac131313@redhat.com>

* NEWS: Cleanup. Use *-linux*-gnu*. Only use `*' for headings.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.82
diff -u -r1.82 NEWS
--- NEWS 1 Aug 2002 17:18:32 -0000 1.82
+++ NEWS 4 Aug 2002 00:00:40 -0000
@@ -5,9 +5,9 @@

* ``gdbserver'' now supports multithreaded applications on some targets

-Support for multithreaded applications using LinuxThreads has been added
-for arm*-*-linux*, i[3456]86-*-linux*, mips*-*-linux*, powerpc*-*-linux*,
-and sh*-*-linux*.
+Support for multithreaded applications using libthread_db has been
+added for arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*,
+mips*-*-linux*-gnu*, powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.

* GDB now supports C/C++ preprocessor macros.

@@ -15,21 +15,16 @@
and provides various commands for showing macro definitions and how
they expand.

+The new command `macro expand EXPRESSION' expands any macro
+invocations in expression, and shows the result.
+
+The new command `show macro MACRO-NAME' shows the definition of the
+macro named MACRO-NAME, and where it was defined.
+
Most compilers don't include information about macros in the debugging
information by default. In GCC 3.1, for example, you need to compile
your program with the options `-gdwarf-2 -g3'. If the macro
information is present in the executable, GDB will read it.
-
-Here are the new commands for working with macros:
-
-** macro expand EXPRESSION
-
-Expand any macro invocations in expression, and show the result.
-
-** show macro MACRO-NAME
-
-Show the definition of the macro named MACRO-NAME, and where it was
-defined.

* Multi-arched targets.