From: "Stephen P. Smith" <ischis2@cox.net>
To: Kevin Buettner <kevinb@redhat.com>, gdb@sources.redhat.com
Subject: Re: shared library support hookin the remote.c
Date: Mon, 28 Jun 2004 21:45:00 -0000 [thread overview]
Message-ID: <40E09084.70108@cox.net> (raw)
In-Reply-To: <20040628134303.20e1cff0@saguaro>
Kevin Buettner wrote:
>
>I think we need more detail. Which functions in remote.c would
>be affected? What would the interface look like and how would
>it be used?
>
>
It would affetc remote_async_wait() and remote_wait(). From the last
time, I know that we don't want to
add extraneous functionality to the remote protocol unless the target
requires it. This method would abstact
that out.
What I haven't figured out is the preferred means of intializing such a
variable across the two subsystems.
There would be a statement something like this:
if ( remote_protocol_solib_hook_funcion )
(*remote_protocol_solib_hook_funcion) ();
Does something like this seem reasonable?
>Also, please note that I am not the maintainer of remote.c...
>
>
>
True - but the use of this pointer would be in the solib area. Since
the target is always queried, this is the way the solib
subsystem would know when it is safe to ask about shared library values
that it needs from a particular target.
sps
next prev parent reply other threads:[~2004-06-28 21:44 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 ` shared library support hookin the remote.c Stephen & Linda Smith
2004-06-28 21:44 ` Kevin Buettner
2004-06-28 21:45 ` Stephen P. Smith [this message]
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=40E09084.70108@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).