From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: Multiple inferiors and memory consumption
Date: Tue, 10 Jul 2012 20:35:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC59791E004D@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <4FFB3F86.2000109@codesourcery.com>
> And now for my real question -- is there any case when using
> multi-process to debug several applications
> not related via parent-child relationship is better than
> running N copies of GDB?
For the sake of completeness, let me mention the obvious.
When doing remote debugging, only one GDB can connect
to the target, so multi-process is the only option to debug
several applications.
Marc
next prev parent reply other threads:[~2012-07-10 20:35 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
2012-07-10 20:35 ` Marc Khouzam [this message]
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=F7CE05678329534C957159168FA70DEC59791E004D@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.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).