diff options
author | Nick Roberts <nickrob@snap.net.nz> | 2005-11-05 10:09:27 +0000 |
---|---|---|
committer | Nick Roberts <nickrob@snap.net.nz> | 2005-11-05 10:09:27 +0000 |
commit | f6e405a269c826b0184480c1983db4421e4449ba (patch) | |
tree | bbf7457b7ec85602741810a1fa66ce3430385ee4 /etc/DEBUG | |
parent | 7dab700a7bfa44e232c7b87c5398a7c5bfb520a7 (diff) | |
download | emacs-f6e405a269c826b0184480c1983db4421e4449ba.tar.gz |
Describe how to provide preprocessor macro information.
Diffstat (limited to 'etc/DEBUG')
-rw-r--r-- | etc/DEBUG | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/etc/DEBUG b/etc/DEBUG index 773737c65c7..0c2739cafc8 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -158,12 +158,13 @@ we want the address of the l-value expression near the bottom of XVECTOR (this_command_keys)->contents[this_command_key_count++] = key; -XVECTOR is a macro, and therefore, in general, GDB does not know about it. -Unless Emacs has been compiled with preprocessor macro info, GDB cannot -evaluate "p XVECTOR (this_command_keys)" . +XVECTOR is a macro, so GDB only knows about it if Emacs has been compiled with +preprocessor macro information. GCC provides this if you specify the options +`-gdwarf-2' and `-g3'. In this case, GDB can evaluate expressions like +"p XVECTOR (this_command_keys)". -However, you can use the xvector command in GDB to get the same -result. Here is how: +When this information isn't available, you can use the xvector command in GDB +to get the same result. Here is how: (gdb) p this_command_keys $1 = 1078005760 |