Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: <gdb-patches@sources.redhat.com>
Subject: [RFA] Small gdbmi.texinfo cleanup
Date: Thu, 13 Jun 2002 22:06:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0206132203220.19373-100000@makita.cygnus.com> (raw)

Hi,

While modifying gdbmi.texinfo for event records, I noticed that several of
the mi command examples were a little off. This patch updates the examples
to reflect reality.

Keith

ChangeLog
2002-06-13  Keith Seitz  <keiths@redhat.com>

        * gdbmi.texinfo: Update command examples with real MI behavior.

Index: gdbmi.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/mi/gdbmi.texinfo,v
retrieving revision 1.26
diff -p -r1.26 gdbmi.texinfo
*** gdbmi.texinfo	25 Feb 2002 02:13:09 -0000	1.26
--- gdbmi.texinfo	14 Jun 2002 05:03:13 -0000
***************
*** 8,14 ****
  @c  @ifinfo
  @c  This file documents GDB/MI, a Machine Interface to GDB.

! @c  Copyright 2000, 2001 Free Software Foundation, Inc.
  @c  Contributed by Cygnus Solutions.

  @c  Permission is granted to copy, distribute and/or modify this document
--- 8,14 ----
  @c  @ifinfo
  @c  This file documents GDB/MI, a Machine Interface to GDB.

! @c  Copyright 2000, 2001, 2002 Free Software Foundation, Inc.
  @c  Contributed by Cygnus Solutions.

  @c  Permission is granted to copy, distribute and/or modify this document
***************
*** 36,42 ****
  @c  @page
  @c  @vskip 0pt plus 1filll

! @c  Copyright @copyright{} 2000, 2001 Free Software Foundation, Inc.

  @c  Permission is granted to copy, distribute and/or modify this document
  @c  under the terms of the GNU Free Documentation License, Version 1.1 or
--- 36,42 ----
  @c  @page
  @c  @vskip 0pt plus 1filll

! @c  Copyright @copyright{} 2000, 2001, 2002 Free Software Foundation, Inc.

  @c  Permission is granted to copy, distribute and/or modify this document
  @c  under the terms of the GNU Free Documentation License, Version 1.1 or
*************** following line is passed to @sc{gdb/mi}
*** 355,361 ****
  the output received from @sc{gdb/mi}.

  @subsubheading Target Stop
!
  Here's an example of stopping the inferior process:

  @example
--- 355,361 ----
  the output received from @sc{gdb/mi}.

  @subsubheading Target Stop
! @c Ummm... There is no "-stop" command. This assumes async, no?
  Here's an example of stopping the inferior process:

  @example
*************** Here's an example of a simple CLI comman
*** 378,384 ****

  @example
  -> print 1+2
! <- ~3\n
  <- (@value{GDBP})
  @end example

--- 378,386 ----

  @example
  -> print 1+2
! <- &"print 1+2\n"
! <- ~"$1 = 3\n"
! <- ^done
  <- (@value{GDBP})
  @end example

*************** Here's what happens if you pass a non-ex
*** 396,402 ****

  @example
  -> -rubbish
! <- error,"Rubbish not found"
  <- (@value{GDBP})
  @end example

--- 398,404 ----

  @example
  -> -rubbish
! <- ^error,msg="Undefined MI command: rubbish"
  <- (@value{GDBP})
  @end example



             reply	other threads:[~2002-06-14  5:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 22:06 Keith Seitz [this message]
2002-06-15 10:26 ` Eli Zaretskii
2002-06-17 10:31   ` Keith Seitz

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=Pine.GSO.4.33.0206132203220.19373-100000@makita.cygnus.com \
    --to=keiths@redhat.com \
    --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