From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remove download_write_size variable
Date: Mon, 31 Jul 2006 17:16:00 -0000 [thread overview]
Message-ID: <u64hdoft4.fsf@gnu.org> (raw)
In-Reply-To: <200607311622.58927.vladimir@codesourcery.com> (message from Vladimir Prus on Mon, 31 Jul 2006 16:22:57 +0400)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Mon, 31 Jul 2006 16:22:57 +0400
> Cc: gdb-patches@sources.redhat.com
>
> > > * symfile.c (download_write_size): Remove.
> > > (show_download_write_size): Remove.
> > > (load_section_callback): Don't use download_write_size.
> > > (_initialize_symfile): Don't register download_write_size.
> >
> > I can find references to download-write-size on the Internet, e.g. in
> > FAQs suggesting how to get better write performance. They all seem to
> > push it as high as memory-write-packet-size, though, which suggests we
> > do not need both limits.
> >
> > I think it's reasonable to remove it. However, you'll have to also
> > remove it from the manual (it's a documented command).
>
> Are you sure? Grep does not find any occurrence in docs, on current mainline.
It's in the node called "Target Commands".
> === gdb/NEWS
> ==================================================================
> --- gdb/NEWS (/mirrors/gdb) (revision 315)
> +++ gdb/NEWS (/patches/download_write_size/gdb) (revision 315)
> @@ -18,6 +18,8 @@
> Kernel Object Display, an embedded debugging feature which only worked with
> an obsolete version of Cisco IOS.
>
> +The 'download_write_size' variable.
> +
This variable is not user-visible. You need to mention the command,
not the C variable.
next prev parent reply other threads:[~2006-07-31 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 12:48 Vladimir Prus
2006-07-18 20:42 ` Daniel Jacobowitz
2006-07-31 12:23 ` Vladimir Prus
2006-07-31 17:16 ` Eli Zaretskii [this message]
2006-08-01 5:34 ` Vladimir Prus
2006-08-02 3:12 ` Eli Zaretskii
2006-08-08 15:49 ` 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=u64hdoft4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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