public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Chris January <chris.january@allinea.com>
To: gdb@sourceware.org
Subject: Re: Multiple inferiors and memory consumption
Date: Thu, 12 Jul 2012 11:01:00 -0000	[thread overview]
Message-ID: <1342090882.2655.0.camel@gumtree> (raw)
In-Reply-To: <87a9z7h1r2.fsf@fleche.redhat.com>

On Tue, 2012-07-10 at 13:09 -0600, Tom Tromey wrote:
> Chris> We have a patch that allows multiple programs_spaces to share the same
> Chris> objfiles by moving the linked list entry into a new struct
> Chris> objfile_instance.
> 
> Presumably this only works if the objfile is mapped at the same address
> in each inferior.

Yes, indeed, so it works well for executables, but less well for shared
libraries.

Chris


  reply	other threads:[~2012-07-12 11:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 20:31 Vladimir Prus
2012-07-10  2:29 ` Tom Tromey
2012-07-10  4:55   ` Vladimir Prus
2012-07-10 19:12     ` Tom Tromey
2012-07-10  8:04 ` Chris January
2012-07-10 19:09   ` Tom Tromey
2012-07-12 11:01     ` Chris January [this message]
2012-07-10 20:35 ` Marc Khouzam
2012-07-10 20:59   ` Paul_Koning
2012-07-10 21:06   ` Vladimir Prus

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=1342090882.2655.0.camel@gumtree \
    --to=chris.january@allinea.com \
    --cc=gdb@sourceware.org \
    /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).