From: Eli Zaretskii <eliz@is.elta.co.il>
To: fnf@ninemoons.com
Cc: gdb-patches@sources.redhat.com, fnf@ninemoons.com
Subject: Re: [RFA] Change auto-solib-add to boolean, add auto-solib-limit
Date: Sun, 28 Oct 2001 01:54:00 -0000 [thread overview]
Message-ID: <200110280853.KAA01884@is.elta.co.il> (raw)
In-Reply-To: <200110271948.f9RJmLd08493@fishpond.ninemoons.com>
> From: Fred Fish <fnf@www.ninemoons.com>
> Date: Sat, 27 Oct 2001 12:48:21 -0700 (MST)
>
> In the current gdb, auto-solib-add is used as both a boolean and as a
> limiting size in megabytes. This patch removes this overloaded
> meaning.
The patches to gdb.texinfo are approved, with the following comments:
> +There are times however when you may wish to not automatically load
I think we need commas on both sides of "however".
> +@kindex set auto-solib-add
> +@item set auto-solib-add @var{mode}
> +Set the shared library symbol autoloading mode. If it is @code{on},
> +symbols from all shared object libraries will be loaded automatically
I think this sentence will be much clearer if you begin it like this:
If @var{mode} is @code{on},
> +new library has been loaded. Otherwise if it is @code{off}, symbols
Same here: Instead of "Otherwise if it is @code{off}", let's say "If
@var{mode} is @code{off}".
> +To explicitly load shared library symbols use the @code{sharedlibrary}
> +command:
This needs a comma after "symbols".
> +reached. This provides the benefit of allowing autoloading to remain on
> +by default while avoiding attempting to autoload excessively large
> +shared libraries, up to a threshold that is initially set but that you
> +can modify if you wish.
This sentence is in a dire need of commas ;-)
Also, "while avoiding attempting to autoload" sounds awkwardly. How
about "but avoids autoloading" instead?
> +@item set auto-solib-limit @var{threshold}
> Set the autoloading size threshold, in megabytes.
This leaves me wondering: can the value of threshold be a fraction,
like 0.5? I think this should be stated in the docs. (Yes, I know
that it was so before your changes.)
Thanks!
next prev parent reply other threads:[~2001-10-28 1:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 12:50 Fred Fish
2001-10-27 17:01 ` Elena Zannoni
2001-10-28 1:54 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 15:35 [RFA] Fix a couple of auto-solib-add problems Fred Fish
2001-10-31 4:02 ` Eli Zaretskii
2001-10-29 20:35 [RFA] Use 1024*1024 for a megabyte, not 1000000 Fred Fish
2001-10-05 12:55 RFC: Avoid calling XXX_skip_prologue for assembly code Fred Fish
2001-10-11 13:13 ` Jim Blandy
2001-10-11 13:37 ` Andrew Cagney
2001-10-11 13:22 ` Jim Blandy
2001-10-11 14:17 ` Jim Blandy
2001-10-11 15:40 ` Andrew Cagney
2001-10-11 19:23 ` Fred Fish
2002-04-11 16:30 ` Fred Fish
2002-04-12 8:34 ` Fernando Nasser
2002-04-12 9:41 ` Fred Fish
2002-04-12 9:47 ` Fernando Nasser
[not found] ` <fnf@www.ninemoons.com>
2001-10-05 13:58 ` Kevin Buettner
2001-10-27 16:38 ` [RFA] Change auto-solib-add to boolean, add auto-solib-limit Kevin Buettner
2001-10-29 22:14 ` [RFA] Use 1024*1024 for a megabyte, not 1000000 Kevin Buettner
2001-10-30 17:22 ` [RFA] Fix a couple of auto-solib-add problems Kevin Buettner
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=200110280853.KAA01884@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=fnf@ninemoons.com \
--cc=gdb-patches@sources.redhat.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