This is the mail archive of the
mailing list for the GDB project.
Re: command api question
Well, maybe if there were a generic method to get/set variables in the
command api. It's possible to do the following from the prompt:
(gdb) set solib-search-path /some/path
(gdb) show solib-search-path
so if there were an easy programmatic way of doing this, then we wouldn't
have to worry about compile time defines.
----- Original Message -----
From: "Daniel Jacobowitz" <email@example.com>
To: "Kris Warkentin" <firstname.lastname@example.org>
Sent: Tuesday, April 02, 2002 2:25 PM
Subject: Re: command api question
> On Tue, Apr 02, 2002 at 02:22:36PM -0500, Kris Warkentin wrote:
> > 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
> > branch someday and we want to keep things as clean as possible. (ie. as
> > changes as possible to common files, most stuff implemented in separate
> > files).
> Well, I also have a solib search path patch that I'd like to get rolled
> in. It's not in an appropriate form right now though. And I think
> there was a third in the list archives over a year ago, that met with
> some opposition.
> I'd really like to see the search path become (at least) compile-time
> default configurable...
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer