From: Kevin Buettner <kevinb@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] solib-svr4.c fetch link map address
Date: Wed, 02 Oct 2002 20:24:00 -0000 [thread overview]
Message-ID: <1021003032440.ZM5911@localhost.localdomain> (raw)
In-Reply-To: Elena Zannoni <ezannoni@redhat.com> "Re: [RFA] solib-svr4.c fetch link map address" (Oct 2, 9:42pm)
On Oct 2, 9:42pm, Elena Zannoni wrote:
> +/* Get the address of the link_map for a given OBJFILE. Loop through
> + the link maps, and return the address of the one corresponding to
> + the given objfile. Note that this function takes into account that
> + objfile can be the main executable, not just a shared library. The
> + main executable has always an empty name field in the linkmap. */
Since this is all sort of experimental at the moment, your patch is
okay. I think we should revisit it at a later time so that we (re)use the
information that's already being fetched by solib-svr4.c. (We'll need
to allocate some space for the link map address though.)
With regard to the main executable, it can either be saved separately,
or put on the so_list chain.
BTW, have you answered Daniel's question about how a gdbserver (or
some other debug agent) should fetch the link map address? I.e,
is something like the qSymbol packet going to be needed?
Kevin
next prev parent reply other threads:[~2002-10-03 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 19:30 Elena Zannoni
2002-10-01 21:52 ` Daniel Jacobowitz
2002-10-02 6:50 ` Elena Zannoni
2002-10-02 10:28 ` Kevin Buettner
2002-10-02 11:42 ` Elena Zannoni
2002-10-02 18:45 ` Elena Zannoni
2002-10-02 20:24 ` Kevin Buettner [this message]
2002-10-02 21:28 ` Daniel Jacobowitz
2002-10-21 11:43 ` Elena Zannoni
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=1021003032440.ZM5911@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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