From a1c2d21e0e23bb792ecf973355480db6f14e4464 Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Thu, 6 Oct 2011 10:55:10 -0400 Subject: [PATCH] * lisp/progmodes/gdb-mi.el (gdb): Doc fix. See http://lists.gnu.org/archive/html/emacs-devel/2011-03/msg00229.html --- lisp/ChangeLog | 4 ++++ lisp/progmodes/gdb-mi.el | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 91f66fcf938..efa4b87a9ea 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,7 @@ +2011-10-06 Chong Yidong + + * progmodes/gdb-mi.el (gdb): Doc fix. + 2011-10-05 Martin Rudalics * window.el (frame-auto-hide-function): New option replacing diff --git a/lisp/progmodes/gdb-mi.el b/lisp/progmodes/gdb-mi.el index a4d7cff4127..a9af1ecf67b 100644 --- a/lisp/progmodes/gdb-mi.el +++ b/lisp/progmodes/gdb-mi.el @@ -605,6 +605,12 @@ NOARG must be t when this macro is used outside `gud-def'" The directory containing FILE becomes the initial working directory and source-file directory for your debugger. +COMMAND-LINE is the shell command for starting the gdb session. +It should be a string consisting of the name of the gdb +executable followed by command-line options. The command-line +options should include \"-i=mi\" to use gdb's MI text interface. +Note that the old \"--anotate\" option is no longer supported. + If `gdb-many-windows' is nil (the default value) then gdb just pops up the GUD buffer unless `gdb-show-main' is t. In this case it starts with two windows: one displaying the GUD buffer and the -- 2.39.2