Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com,  gdb-patches@sources.redhat.com
Subject: Re: MI solib notification
Date: Wed, 18 Feb 2009 20:04:00 -0000	[thread overview]
Message-ID: <200902182250.39997.vladimir@codesourcery.com> (raw)
In-Reply-To: <uiqn7vb0x.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Wednesday 18 February 2009 21:46:06 Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Wed, 18 Feb 2009 10:31:02 +0300
> > Cc: gdb-patches@sources.redhat.com
> > 
> > > But I'm okay with your original text as well, as I said.
> > 
> > Ok, I've checked in that patch.
> 
> Thanks.
> 
> > +@var{host-name}, and @var{symbols-loaded}. The @var{id} field is an
>                                             ^^
> One more blank here, please.
> 
> > +library file on the target, and on the host respectively. For native
>                                                            ^^
> Likewise.
> 
> > +debugging, both those fields have the same value. The
>                                                    ^^
> Likewise.
> 
> > +Reports that a library was unloaded by the program. This notification
>                                                      ^^
> Likewise.

I've checked in the below follow-up.

Thanks,
Volodya


[-- Attachment #2: spaces.diff --]
[-- Type: text/x-diff, Size: 1984 bytes --]

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
retrieving revision 1.866
diff -u -p -r1.866 ChangeLog
--- ChangeLog	18 Feb 2009 07:28:33 -0000	1.866
+++ ChangeLog	18 Feb 2009 19:43:24 -0000
@@ -1,5 +1,10 @@
 2009-02-18  Vladimir Prus  <vladimir@codesourcery.com>
 
+	* gdb.texinfo (GDB/MI Async Records): Add double-spaces
+	between sentences.
+
+2009-02-18  Vladimir Prus  <vladimir@codesourcery.com>
+
 	* gdb.texinfo (GDB/MI Async Records): Document the
 	=library-loaded and =library-unloaded notifications.
 
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.559
diff -u -p -r1.559 gdb.texinfo
--- gdb.texinfo	18 Feb 2009 07:28:33 -0000	1.559
+++ gdb.texinfo	18 Feb 2009 19:43:26 -0000
@@ -19915,16 +19915,16 @@ that thread.
 @item =library-loaded,...
 Reports that a new library file was loaded by the program.  This
 notification has 4 fields---@var{id}, @var{target-name},
-@var{host-name}, and @var{symbols-loaded}. The @var{id} field is an
+@var{host-name}, and @var{symbols-loaded}.  The @var{id} field is an
 opaque identifier of the library.  For remote debugging case,
 @var{target-name} and @var{host-name} fields give the name of the
-library file on the target, and on the host respectively. For native
-debugging, both those fields have the same value. The
+library file on the target, and on the host respectively.  For native
+debugging, both those fields have the same value.  The
 @var{symbols-loaded} field reports if the debug symbols for this
 library are loaded.
 
 @item =library-unloaded,...
-Reports that a library was unloaded by the program. This notification
+Reports that a library was unloaded by the program.  This notification
 has 3 fields---@var{id}, @var{target-name} and @var{host-name} with
 the same meaning as for the @code{=library-loaded} notification
 

  reply	other threads:[~2009-02-18 19:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 23:44 Vladimir Prus
     [not found] ` <utz7gzcmo.fsf@gnu.org>
2009-02-01 17:53   ` Daniel Jacobowitz
2009-02-01 18:22     ` Eli Zaretskii
2009-02-01 18:29       ` Daniel Jacobowitz
2009-02-17 19:09         ` Vladimir Prus
2009-02-17 19:45           ` Eli Zaretskii
2009-02-17 19:49             ` Vladimir Prus
2009-02-17 20:30               ` Eli Zaretskii
2009-02-17 21:45                 ` Vladimir Prus
2009-02-17 21:59                   ` Vladimir Prus
2009-02-18  7:31                     ` Eli Zaretskii
2009-02-18 10:19                       ` Vladimir Prus
2009-02-18 19:53                         ` Eli Zaretskii
2009-02-18 20:04                           ` Vladimir Prus [this message]
2009-02-18 22:28                             ` Eli Zaretskii
2009-02-18  4:24                   ` Eli Zaretskii
2009-02-17 21:37               ` Daniel Jacobowitz
2009-02-17 22:10               ` Pedro Alves
2009-02-18  2:01                 ` Pedro Alves
2009-02-01 18:04 ` Daniel Jacobowitz
2009-02-12  9:12   ` Vladimir Prus
2009-02-12 13:22     ` Daniel Jacobowitz
2009-02-12 15:02       ` Vladimir Prus
2009-02-12 15:13         ` Daniel Jacobowitz
2009-02-12 17:35           ` Tom Tromey
2009-02-12 18:02             ` Daniel Jacobowitz
2009-02-12 20:11               ` Tom Tromey
2009-02-12 20:17                 ` Vladimir Prus
2009-02-12 20:26                   ` Daniel Jacobowitz
2009-02-17 19:08                     ` Vladimir Prus
2009-02-12 18:06           ` Pedro Alves
2009-02-12 19:45             ` Pedro Alves
2009-02-12 19:56             ` Tom Tromey
2009-02-12 19:58               ` Daniel Jacobowitz
2009-02-13  2:22               ` Joel Brobecker
2009-02-01 18:47 ` Daniel Jacobowitz

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=200902182250.39997.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pedro@codesourcery.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