Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb@sources.redhat.com>
Subject: how to access show/set data
Date: Thu, 02 Jan 2003 19:44:00 -0000	[thread overview]
Message-ID: <013201c2b297$566460e0$0202040a@catdog> (raw)

Say, for example, I wanted to programmatically modify solib_search_path, a
static char * which is declared in solib.c.

I know a pointer to it has been stored via the add_set_cmd function and I'm
wondering if there is a "approved" way for me to dig out this pointer.  I
have an OS dependent init file that needs to monkey with solib_search_path
and I didn't want to make the mods to solib.c or to make a "qnx_solib.c" for
such a small thing.

cheers,

Kris


             reply	other threads:[~2003-01-02 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 19:44 Kris Warkentin [this message]
2003-01-02 20:59 ` Kris Warkentin
2003-01-04  2:19   ` GDB 5.2/5.3 breakpoint bug Sunil Alankar
2003-01-04  2:23     ` Daniel Jacobowitz
2003-01-08 23:16 ` how to access show/set data Kevin Buettner
2003-01-09 13:31   ` Kris Warkentin
2003-01-09 18:20     ` Christopher Faylor
2003-01-09 18:50       ` Kris Warkentin
2003-01-09 18:52         ` Kris Warkentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='013201c2b297$566460e0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox