From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [v6] multi-executable support
Date: Mon, 05 Oct 2009 15:59:00 -0000 [thread overview]
Message-ID: <200910051659.20885.pedro@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Here's my current patch to add multi-executable support to GDB.
Following the last discussion,
http://sourceware.org/ml/gdb-patches/2009-09/msg00194.html
This makes it so that there's always an inferior, and the
"symbol-spaces" are relegated to the background as an implementation
detail, renamed as program spaces.
This is almost the same as the patch I had posted on the link
above as "v5", with s/symbol-spaces/program-spaces/, generally
cleaned up, and documentation updated to reflect the simpler
model and to address other points Eli raised previously.
I'm hoping this isn't far from putting in, as it's been
a nuisance getting this patch close to mainline, as it
tends to regress easily due to new code going in that
doesn't consider multi-exec.
Eli, could you please take a new look at the docs bits?
I may have missed something, but I hope nothing big.
Note: the changeLogs are a bit stale and needs a
new update.
No regressions on x86_64-unknown-linux-gnu.
--
Pedro Alves
[-- Attachment #2: multiexec_v6.diff.gz --]
[-- Type: application/x-gzip, Size: 80507 bytes --]
next reply other threads:[~2009-10-05 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 15:59 Pedro Alves [this message]
2009-10-05 21:57 ` Eli Zaretskii
2009-10-06 12:14 ` Pedro Alves
2009-10-06 14:29 ` Eli Zaretskii
2009-10-12 1:26 ` [v7] " Pedro Alves
2009-10-12 19:09 ` Eli Zaretskii
2009-10-13 13:40 ` [v8] " Pedro Alves
2009-10-14 3:03 ` Joel Brobecker
2009-10-14 15:16 ` Pedro Alves
2009-10-14 15:28 ` Joel Brobecker
2009-10-14 16:25 ` Tom Tromey
2009-10-14 16:48 ` Pedro Alves
2009-10-14 17:41 ` Tom Tromey
2009-10-06 5:13 ` [v6] " Sérgio Durigan Júnior
2009-10-06 13:55 ` Pedro Alves
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=200910051659.20885.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@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