From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: <gdb@sourceware.org>
Subject: Re: Multiple inferiors and memory consumption
Date: Tue, 10 Jul 2012 02:29:00 -0000 [thread overview]
Message-ID: <87zk78ic2b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4FFB3F86.2000109@codesourcery.com> (Vladimir Prus's message of "Tue, 10 Jul 2012 00:31:02 +0400")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> That is, it does not seem like GDB notices that symbol tables
Volodya> of all 4 loaded executables are identical
Volodya> Is this something that is going to be improved upon in future?
I've been working on it off and on.
You can see my latest attempt, search for
[0/17] RFC: share minimal symbols across objfiles
in the Dec 2011 archives.
There are some follow-up thoughts scattered through the subsequent
months. The problem is reasonably hard -- those 17 patches only address
minsym sharing, but there is at least partial- and full-symbol sharing
to deal with as well; plus some other things making it harder (dlmopen
support, should we want it, makes a mess of it all).
Volodya> And now for my real question -- is there any case when using
Volodya> multi-process to debug several applications
Volodya> not related via parent-child relationship is better than running N
Volodya> copies of GDB?
Nothing today.
In the future they'll share debuginfo when possible, but that may be the
only advantage.
I've occasionally wondered whether we could have gdb fork when in MI
mode and it follows both parent and child.
Tom
next prev parent reply other threads:[~2012-07-10 2:29 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 [this message]
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
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=87zk78ic2b.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=vladimir@codesourcery.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).