Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stephen & Linda Smith <ischis2@cox.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: Kevin Buettner <kevinb@redhat.com>,  gdb@sources.redhat.com
Subject: Re: shared library support hookin the remote.c
Date: Wed, 14 Jul 2004 18:44:00 -0000	[thread overview]
Message-ID: <40F57B9C.6020704@cox.net> (raw)
In-Reply-To: <40F57685.7020108@gnu.org>


Andrew Cagney wrote:

>
> So each time the inferior stops, GDB will need to re-poll for shlib 
> changes?

That is the way I currently have it set up.

There is one thing I don't understand about the F packet. How does the 
inferior know that it is OK to send the packet. From everything that I 
have read. Comunication is initiated by GDB and answered by the 
inferior. I didn't know that the stub could initiate a packet. If so, Do 
I just tack on the F packet information to the end of a currently 
generated packet?

This is the reason I was polling. Otherwise I prefer to not poll.

>
> Can the stub instead generate a packet, very like the recently added F 
> (File I/O) indicating that the link map changed (and what)?

I think I have answered this by answering the preceding question.

>
> The other is to have a custom xxx-shlib hooked up to inferior stopped 
> that queries for the stuff you describe. It could probably be tunneled 
> as a TARGET_OBJECT_KOD packet.
>
If I implement the F packet would that get rid if the need for a xxx-shlib?



  reply	other threads:[~2004-07-14 18:30 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
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 [this message]
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=40F57B9C.6020704@cox.net \
    --to=ischis2@cox.net \
    --cc=cagney@gnu.org \
    --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