Re: [patch] Fix handling of elided libthread-db-search-path values.

[Doug Evans <dje@google.com>]

On Tue, May 10, 2011 at 10:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 10 May 2011 09:59:18 -0700 (PDT)
>> From: dje@google.com (Doug Evans)
>>
>> 2) There's an assumption that the default value for libthread-db-search-path
>>    is always an empty list.
>>
>> That's true, but only because no one overrides LIBTHREAD_DB_SEARCH_PATH.
>
> But the new text doesn't mention LIBTHREAD_DB_SEARCH_PATH at all.  So
> it leaves the reader in the darkness wrt the default value and where
> will it come from.

Yeah, that's a gdb macro, didn't want to mention it in the user docs.
But ok, how about this?

If you omit @var{path}, @samp{libthread-db-search-path} will be reset to
its default value (an empty list on @sc{gnu}/Linux and Solaris systems).
Internally, the default value comes from the @code{LIBTHREAD_DB_SEARCH_PATH}
macro.

>> -@samp{libthread-db-search-path} will be reset to an empty list.
>> +@samp{libthread-db-search-path} will be reset to the its value.
>                                           ^^^^^^^^^^^^^^^^^^^^^^
> A typo.

Yeah, fixed in what's checked in.