From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: MultiProcess branch mentioned in the wiki
Date: Tue, 16 Dec 2008 01:04:00 -0000 [thread overview]
Message-ID: <m3fxkpvsq2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200812081653.44594.pedro@codesourcery.com> (Pedro Alves's message of "Mon\, 8 Dec 2008 16\:53\:44 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> I've finally drafted a wiki page for the multi-process /
Pedro> multi-exec work. Check it out at:
Pedro> http://sourceware.org/gdb/wiki/MultiProcess
Thanks. I read through this.
About the shared library support: I also didn't see a mention of how
objfiles will be handled. On the one hand, it seems important to
share them across inferiors. On the other hand, IIUC, they are
relocated; so sharing will be hard due to address space randomization.
Maybe this just isn't on your immediate list?
Also, if you know offhand what is involved in "Linux native support",
that would be interesting information to have.
Tom
prev parent reply other threads:[~2008-12-16 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 16:54 Pedro Alves
2008-12-08 17:22 ` Jeremy Bennett
2008-12-08 17:39 ` Joel Brobecker
2008-12-16 1:04 ` Tom Tromey [this message]
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=m3fxkpvsq2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=pedro@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