Patch to build gdb-5.0 with readline-4.1

[Eli Zaretskii]

> From: Elena Zannoni <ezannoni@cygnus.com>
> Date: Wed, 5 Jul 2000 18:20:05 -0400 (EDT)
> 
> Andrew Cagney writes:
>  > Michael Snyder wrote:
>  > 
>  > > Well, we went thru the same struggle the last time we merged
>  > > with readline.  Maybe it would save trouble if we just renamed
>  > > our version of savestring (which I believe is unrelated to the
>  > > readline version) to gdb_savestring.  Then we could forget
>  > > about it, and future readline merges might be less troublesome.
>  > 
>  > Well, part of my todo list is to get savestring() replaced by something
>  > in libiberty. (like liberty:xstrdup() is slowly replaceing strsave()). 
>  > There is (a slightly irksum) xmemdup() available, perhaphs there could
>  > be xstrldup() (and so I start a flame war about string duplicate
>  > function interfaces :-).
>  > 
> 
> Do we have a preference on this? I would like to follow Michael's
> suggestion.

Either gdb_savestring or libiberty's xstrdup is fine, I think.
Perhaps the latter is better, since we already use libiberty.