Re: command api question

["Kris Warkentin" <kewarken@qnx.com>]

Is that an agreeable solution?  Or would it be better to just provide
get/set functions?  We're hoping to get our changes rolled into the gdb head
branch someday and we want to keep things as clean as possible. (ie. as few
changes as possible to common files, most stuff implemented in separate qnx
files).

cheers,

Kris
----- Original Message -----
From: "Daniel Jacobowitz" <drow@mvista.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: <gdb@sources.redhat.com>
Sent: Tuesday, April 02, 2002 1:55 PM
Subject: Re: command api question


> On Tue, Apr 02, 2002 at 01:51:16PM -0500, Kris Warkentin wrote:
> > There is a static variable 'solib_search_path' in solib.c that I'd like
to
> > get access to outside of solib.c.  I see that it has been added to the
> > command list with an 'add_set_cmd()' call.  What is the easiest way for
me
> > to get a reference to this variable so that I can modify it? (we have an
> > initialization routine to set a default solib search path).  I apologize
if
> > this is clearly documented somewhere - the functions in command.h are
> > probably what I'm looking for but it wasn't immediately obvious which
one I
> > should use and how.
>
> It's probably easier just to make it into a global, instead of munging
> the command lists.
>
> --
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer
>