From: Stephen & Linda Smith <ischis2@cox.net>
To: gdb <gdb@sources.redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>
Subject: shared library support hookin the remote.c
Date: Thu, 24 Jun 2004 01:55:00 -0000 [thread overview]
Message-ID: <40DA349C.6080607@cox.net> (raw)
In-Reply-To: <20040611141424.2bed79f7@saguaro>
I have been trying to decide how to hook the solib support into the remote protocol and think that what is needed is a pointer to a function in remote.c.
Initially the pointer would be initailized to null (zero) and wouldn't be used unless the
solib supporting code initialized it to point to one of target specific functions. The reason I came up with this idea is that the data that is needed by solib would in general not be the same between targets. Also this would keep the code that is to handle this extension out of the remote.c file which is general in nature.
With this resolved I think I can start coding (starting by adding this variable to the tree). It doesn't make much sense to write the solib support if I can't get the data out of the remote target.
What do you think
next prev parent reply other threads:[~2004-06-24 1:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 21:05 shared library support Stephen P. Smith
2004-05-21 20:49 ` Stephen P. Smith
2004-06-11 21:14 ` Kevin Buettner
2004-06-24 1:55 ` Stephen & Linda Smith [this message]
2004-06-28 21:44 ` shared library support hookin the remote.c Kevin Buettner
2004-06-28 21:45 ` Stephen P. Smith
2004-06-29 1:55 ` Kevin Buettner
2004-06-29 1:56 ` Stephen & Linda Smith
2004-07-01 17:58 ` Kevin Buettner
2004-07-02 20:20 ` Andrew Cagney
2004-07-02 21:16 ` Stephen P. Smith
2004-07-02 22:30 ` Andrew Cagney
2004-07-13 20:15 ` Stephen P. Smith
2004-07-14 18:30 ` Andrew Cagney
2004-07-14 18:44 ` Stephen & Linda Smith
2004-07-14 19:05 ` Dave Korn
2004-07-14 19:29 ` Andrew Cagney
2004-07-02 21:25 ` Kevin Buettner
2004-07-02 22:25 ` Andrew Cagney
2004-07-02 23:22 ` Kevin Buettner
2004-07-08 15:04 ` Andrew Cagney
2004-07-28 3:04 ` Kevin Buettner
2004-08-03 14:58 ` Andrew Cagney
2004-06-29 2:13 Stephen & Linda Smith
2004-06-29 6:27 ` Stephen & Linda Smith
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=40DA349C.6080607@cox.net \
--to=ischis2@cox.net \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).