From: Pedro Alves <pedro@codesourcery.com>
To: teawater <teawater@gmail.com>
Cc: tromey@redhat.com, "Stan Shebs" <stan@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [multiprocess PING] Three patches for focus_command and linux-nat target
Date: Wed, 10 Dec 2008 04:03:00 -0000 [thread overview]
Message-ID: <200812100402.53290.pedro@codesourcery.com> (raw)
In-Reply-To: <daef60380812091911u1ce0954crd6337367f54aa93c@mail.gmail.com>
On Wednesday 10 December 2008 03:11:28, teawater wrote:
> Sorry to disturb you.
Sorry, I've been caught up with other things.
> Could you please help me review these patches for multiprocess branch
> or give me some advices for it?
>
> http://sourceware.org/ml/gdb-patches/2008-11/msg00713.html
> This one is for memory leak of focus_command.
This bit is Stan's code, but it looks OK to me.
>
> http://sourceware.org/ml/gdb-patches/2008-12/msg00001.html
This is really going in the wrong direction, and probably makes the
checkpoints.exp, multi-forks.exp etc. tests bomb out even more.
If you can be a bit more patient, I'm trying to find time to clean up
a bunch of patches I have here that add proper multi-process support
to the native linux target.
> http://sourceware.org/ml/gdb-patches/2008-12/msg00058.html
> These ones is for linux-nat target.
I'd really like to not extend this hack further. The caller
upstack should have switched inferior_ptid itself, and if
this is a memory read, trying to read off a proto-inferior, well,
we have to decide how to handle it, patches/proposals/questions
comming as soon as I find a bit of time.
--
Pedro Alves
prev parent reply other threads:[~2008-12-10 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 3:12 teawater
2008-12-10 4:03 ` Pedro Alves [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=200812100402.53290.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
--cc=teawater@gmail.com \
--cc=tromey@redhat.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