This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: MI solib notification
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: vladimir at codesourcery dot com, gdb-patches at sources dot redhat dot com, nickrob at snap dot net dot nz
- Date: Sun, 01 Feb 2009 20:22:28 +0200
- Subject: Re: MI solib notification
- References: <200901310010.46738.vladimir@codesourcery.com> <utz7gzcmo.fsf@gnu.org> <20090201175309.GA4597@caradoc.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sun, 1 Feb 2009 12:53:09 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>,
> gdb-patches@sources.redhat.com, nickrob@snap.net.nz
>
> > > +@item =library-loaded,id="@var{id}",target-name="@var{target-name}",host-name="@var{host-name}",low-address="@var{low}",high-address="@var{high}",symbols-loaded="@var{loaded}"
> >
> > This is a very long line, and the @table that it's part of has @code
> > markup, which means TeX will not break this line. We need to make it
> > shorter. One idea is this:
> >
> > @item =library-loaded,@var{info}
> >
> > and then describe the contents of @var{info} below, perhaps as a
> > separate @table. WDYT?
>
> MI output comes all on one line, but what we've done elsewhere in the
> GDB/MI chapter is insert line breaks after some of the commas. How
> about that here too?
That'd be okay as well, although I don't really understand why it is
better than my suggestion.