Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
		  Pedro Alves <pedro_alves@portugalmail.pt>
Subject: Re: [rfc] Shared libraries over the remote protocol, take two
Date: Mon, 18 Jun 2007 20:10:00 -0000	[thread overview]
Message-ID: <m3hcp5qb05.fsf@codesourcery.com> (raw)
In-Reply-To: <20070618150211.GA23415@caradoc.them.org> (Daniel Jacobowitz's message of "Mon, 18 Jun 2007 11:02:11 -0400")


Daniel Jacobowitz <drow@false.org> writes:
> +/* Private data for each loaded library.  */
> +struct lm_info
> +{
> +  /* The library's name.  The name is normally kept in the struct
> +     so_list; it is only here during XML parsing.  */
> +  char *name;
> +
> +  /* The number of entries in SEGMENT_BASES.  */
> +  int num_bases;
> +
> +  /* The base addresses for each independently relocatable segment of
> +     this shared library.  */
> +  CORE_ADDR *segment_bases;
> +
> +  /* The cached offsets for each section of this shared library,
> +     determined from SEGMENT_BASES.  */
> +  struct section_offsets *offsets;
> +};

I'm not too familiar with VECs, but is there some reason not to use a
VEC for segment_bases, as well?


  parent reply	other threads:[~2007-06-18 20:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 15:02 Daniel Jacobowitz
2007-06-18 19:32 ` Jim Blandy
2007-06-18 19:38   ` Daniel Jacobowitz
2007-06-18 22:04     ` Jim Blandy
2007-06-18 22:20       ` Daniel Jacobowitz
2007-06-18 20:05 ` Eli Zaretskii
2007-07-02 19:03   ` Daniel Jacobowitz
2007-06-18 20:10 ` Jim Blandy [this message]
2007-06-18 20:13 ` Jim Blandy
2007-06-18 20:33   ` Daniel Jacobowitz
2007-06-18 22:06     ` Jim Blandy
2007-06-18 21:13 ` Pedro Alves
2007-07-02 22:01 ` Daniel Jacobowitz

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=m3hcp5qb05.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    --cc=uweigand@de.ibm.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