summaryrefslogtreecommitdiff
path: root/gdb
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
commit49019d54d1b5016a2644dbc3cd623916e6b9e13e (patch)
tree7c84239f07a82f29cd543e815d2e092f1c56c7c3 /gdb
parentc030f66af23afc97b401491aa51342bdcde886da (diff)
downloadgdb-49019d54d1b5016a2644dbc3cd623916e6b9e13e.tar.gz
* NEWS: Note addition of macro support.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog2
-rw-r--r--gdb/NEWS22
2 files changed, 24 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 1b95736db7d..d4a95e093cc 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,7 @@
2002-05-17 Jim Blandy <jimb@redhat.com>
+ * NEWS: Note addition of macro support.
+
Expand preprocessor macros in C expressions.
* c-lang.h: #include "macroexp.h", for macro_lookup_ftype.
(scan_macro_expansion, scanning_macro_expansion,
diff --git a/gdb/NEWS b/gdb/NEWS
index 468158f76f2..191c8c9f679 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-*-*