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 19:12:00 -0000 [thread overview]
Message-ID: <87629vh1ls.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4FFBB5C3.3000601@codesourcery.com> (Vladimir Prus's message of "Tue, 10 Jul 2012 08:55:31 +0400")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> Though I'm thinking that single GDB might allow easier
Volodya> implementation of possible cool things like "step through DBus
Volodya> call". Or anything where direct access to two, or several,
Volodya> processes, is needed. Of course, we can do this via IDE, but
Volodya> with remote debugging that might end up awkward/slow.
Yeah, I think there may be some useful features along these lines that
could be done. There's nothing pre-canned, though.
I do tend to think that debugging multiple totally unrelated inferiors
is unusual. That is, gdb will probably provide more benefit than you
might ordinarily expect.
Though, based on bug reporting rates, I think any kind of multi-inferior
debugging is still very rare.
Tom
next prev parent reply other threads:[~2012-07-10 19:12 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 [this message]
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=87629vh1ls.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).