Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] MI Doco
Date: Fri, 02 Jun 2006 00:23:00 -0000	[thread overview]
Message-ID: <17535.33986.598009.914783@kahikatea.snap.net.nz> (raw)


The second half of the node "Program Control" has a list of commands which
clearly don't aren't about program control.  Having repeatedly spent too
much time looking for -file-list-exec-source-files, I've split the node in
two.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


2006-06-02  Nick Roberts  <nickrob@snap.net.nz>

	(GDB/MI Files):  New Node split from Program Control.


*** gdb.texinfo	02 Jun 2006 11:30:46 +1200	1.334
--- gdb.texinfo	02 Jun 2006 11:48:33 +1200	
*************** Elena Zannoni.
*** 17261,17266 ****
--- 17261,17267 ----
  * GDB/MI Breakpoint Table Commands::
  * GDB/MI Data Manipulation::
  * GDB/MI Program Control::
+ * GDB/MI Files::
  * GDB/MI Miscellaneous Commands::
  @ignore
  * GDB/MI Kod Commands::
*************** file="recursive2.c",fullname="/home/foo/
*** 19520,19525 ****
--- 19521,19529 ----
  Is this going away????
  @end ignore
  
+ @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ @node GDB/MI Files
+ @section @sc{gdb/mi} Files
  
  @subheading The @code{-file-exec-and-symbols} Command
  @findex -file-exec-and-symbols


             reply	other threads:[~2006-06-02  0:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02  0:23 Nick Roberts [this message]
2006-06-02  9:05 ` Eli Zaretskii
2006-06-02 10:23   ` Nick Roberts
2006-06-02 10:44     ` Eli Zaretskii
2006-06-03 23:57       ` Nick Roberts
2006-06-04 19:32         ` Eli Zaretskii
2006-06-09 19:07         ` Eli Zaretskii
2006-06-09 19:12           ` Daniel Jacobowitz
2006-06-09 19:52             ` Eli Zaretskii
2006-06-09 19:57               ` Daniel Jacobowitz
2006-06-10  7:32                 ` Eli Zaretskii
2006-07-01 12:35                   ` [commit] Fix MI prompt in manual (was: MI Doco) Eli Zaretskii
2006-06-09 19:58               ` [PATCH] MI Doco Bob Rossi
2006-06-09 23:27           ` Nick Roberts
2006-06-10  7:51             ` Eli Zaretskii
2006-06-10 21:40               ` Nick Roberts
2006-06-11  3:31                 ` Eli Zaretskii
2006-06-11 10:47                   ` Nick Roberts
2006-06-11 19:27                     ` Eli Zaretskii
2006-06-11 21:42                       ` Nick Roberts
2006-06-12  3:36                         ` Eli Zaretskii
2006-06-12  6:19                           ` Nick Roberts
2006-06-13  3:39                             ` Eli Zaretskii
2006-06-13  4:46                               ` Nick Roberts
2006-06-13 17:26                                 ` Eli Zaretskii
2006-06-13 21:15                                   ` Nick Roberts
2006-06-14 18:30                                     ` Eli Zaretskii
2006-06-14 21:05                                       ` Nick Roberts
2006-06-15  6:56                                         ` Eli Zaretskii
2006-06-30  2:13                                           ` Nick Roberts
2006-06-30 12:09                                             ` Eli Zaretskii
2006-06-30 14:12                                               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17535.33986.598009.914783@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox