Re: [PATCH 5/7] CLI: add --leak-report top level option

Subject: Re: [PATCH 5/7] CLI: add --leak-report top level option

Date: Sun, 20 Jan 2013 13:55:14 -0800

To: david@tethera.net, notmuch@notmuchmail.org

Cc: David Bremner

From: Jameson Graef Rollins


On Sat, Jan 19 2013, david@tethera.net wrote:
> This roughly mimics the samba4 argument. The presence of the command
> line argument overrides any value of NOTMUCH_TALLOC_REPORT in the
> environment.
> ---
>  man/man1/notmuch.1 |    8 ++++++++
>  notmuch.c          |   18 +++++++-----------
>  2 files changed, 15 insertions(+), 11 deletions(-)
>
> diff --git a/man/man1/notmuch.1 b/man/man1/notmuch.1
> index 6bf9b2e..5c58c41 100644
> --- a/man/man1/notmuch.1
> +++ b/man/man1/notmuch.1
> @@ -70,6 +70,14 @@ Print a synopsis of available commands and exit.
>  Print the installed version of notmuch, and exit.
>  .RE
>  
> +.RS 4
> +.TP 4
> +.BI \-\-leak-report= path
> +
> +Write a detailed report of all memory allocated via talloc to
> +.I path
> +.RE

Do we really need a command line option for this?  Why isn't the env var
sufficient?  This just seems to me like it clutters the interface, for
an option that is purely for debugging and should rarely if ever be used
by most users.

jamie.
part-000.sig (application/pgp-signature)

Thread: