From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24194 invoked by alias); 1 Feb 2009 18:22:52 -0000 Received: (qmail 24185 invoked by uid 22791); 1 Feb 2009 18:22:52 -0000 X-SWARE-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BARRACUDA_BRBL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 01 Feb 2009 18:22:45 +0000 Received: from conversion-daemon.i_mtaout5.012.net.il by i_mtaout5.012.net.il (HyperSendmail v2004.12) id <0KEE00K00G5IN400@i_mtaout5.012.net.il> for gdb-patches@sources.redhat.com; Sun, 01 Feb 2009 20:22:50 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.109.18]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KEE00NEYGDW36V4@i_mtaout5.012.net.il>; Sun, 01 Feb 2009 20:22:46 +0200 (IST) Date: Sun, 01 Feb 2009 18:22:00 -0000 From: Eli Zaretskii Subject: Re: MI solib notification In-reply-to: <20090201175309.GA4597@caradoc.them.org> To: Daniel Jacobowitz Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com, nickrob@snap.net.nz Reply-to: Eli Zaretskii Message-id: References: <200901310010.46738.vladimir@codesourcery.com> <20090201175309.GA4597@caradoc.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00003.txt.bz2 > Date: Sun, 1 Feb 2009 12:53:09 -0500 > From: Daniel Jacobowitz > Cc: Vladimir Prus , > 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.