aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNick Roberts2005-11-03 02:03:24 +0000
committerNick Roberts2005-11-03 02:03:24 +0000
commit0a24fa80376ce7ef6e765806922cf95642a4ea8f (patch)
tree73fa29228ab83ce7ffd632feedbef697d00b988c
parent99ac518222a3ec7c3cd5684bc6a4165dade3998d (diff)
downloademacs-0a24fa80376ce7ef6e765806922cf95642a4ea8f.tar.gz
emacs-0a24fa80376ce7ef6e765806922cf95642a4ea8f.zip
(Note): GDB can sometimes expand macros.
-rw-r--r--etc/DEBUG5
1 files changed, 3 insertions, 2 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index 27f563a7405..773737c65c7 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -158,8 +158,9 @@ we want the address of the l-value expression near the bottom of
158 158
159 XVECTOR (this_command_keys)->contents[this_command_key_count++] = key; 159 XVECTOR (this_command_keys)->contents[this_command_key_count++] = key;
160 160
161XVECTOR is a macro, and therefore GDB does not know about it. 161XVECTOR is a macro, and therefore, in general, GDB does not know about it.
162GDB cannot evaluate "p XVECTOR (this_command_keys)". 162Unless Emacs has been compiled with preprocessor macro info, GDB cannot
163evaluate "p XVECTOR (this_command_keys)" .
163 164
164However, you can use the xvector command in GDB to get the same 165However, you can use the xvector command in GDB to get the same
165result. Here is how: 166result. Here is how: