aboutsummaryrefslogtreecommitdiff
path: root/gdb/NEWS
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2002-05-17 18:02:20 +0000
committerJim Blandy <jimb@codesourcery.com>2002-05-17 18:02:20 +0000
commite0e9281e471adb9bf226b0372f4330dad1277ebc (patch)
tree9b450c1030fa3084dacb01ce3fa3df67cd8ecfc2 /gdb/NEWS
parente2e0bcd1165b49ead57fd9e55e6797817a07c7fb (diff)
downloadgdb-e0e9281e471adb9bf226b0372f4330dad1277ebc.zip
gdb-e0e9281e471adb9bf226b0372f4330dad1277ebc.tar.gz
gdb-e0e9281e471adb9bf226b0372f4330dad1277ebc.tar.bz2
* NEWS: Note addition of macro support.
Diffstat (limited to 'gdb/NEWS')
-rw-r--r--gdb/NEWS22
1 files changed, 22 insertions, 0 deletions
diff --git a/gdb/NEWS b/gdb/NEWS
index 468158f..191c8c9 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,6 +3,28 @@
*** Changes since GDB 5.2:
+* GDB now supports C/C++ preprocessor macros.
+
+GDB now expands preprocessor macro invocations in C/C++ expressions,
+and provides various commands for showing macro definitions and how
+they expand.
+
+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.
NEC V850 v850-*-*