This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] new command to search memory
> Date: Thu, 14 Feb 2008 14:51:40 -0800
> From: "Doug Evans" <dje@google.com>
> Cc: gdb-patches@sourceware.org
>
> On Thu, Feb 14, 2008 at 11:53 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Wed, 13 Feb 2008 18:19:15 -0800 (PST)
> > > From: dje@google.com (Doug Evans)
> >
> > >
> > > I didn't get a response to the non-doc portions of this patch.
> > > [Eli, thanks for the doc review, I made the suggested changes,
> > > though I went a different route in shortening the length of the
> > > line specifying the find command syntax. The end result is still
> > > rather short.]
> >
> > You mean, rather long...
> >
> > The patch is okay with me, but could you (or someone else) please see
> > whether these two long lines
> >
> >
> > > +@item find @r{[}/@var{sn}@r{]} @var{start_addr}, @@@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
> > > +@itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
> >
> > survive the typesetting for the printed manual (either by TeX or
> > pdftex) without overflowing the page margin? I'm afraid they will
> > overflow, since the items of this table are typeset with @code, and
> > @code specifies a chunk of monospaced font that cannot be broken
> > between lines.
>
> Is looking at gdb.pdf (created with cd doc && make gdb.pdf) sufficient?
Yes, thanks.