From: Pedro Alves <pedro@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver/RFC/RFA] Implement multiprocess extensions, add linux multiproces support.
Date: Wed, 01 Apr 2009 23:30:00 -0000 [thread overview]
Message-ID: <200904020030.08885.pedro@codesourcery.com> (raw)
In-Reply-To: <ufxgulv38.fsf@gnu.org>
On Monday 30 March 2009 19:32:59, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Mon, 30 Mar 2009 15:28:00 +0100
> >
> > This patch adds multiprocess support to gdbserver.
>
> Thanks.
>
> If this is approved, I think we will want a NEWS entry.
Agreed. But, these gdbserver multiprocess changes aren't
much user visible yet. We need gdb changes to expose this extra
functionality, and to make it more useful. I was thinking of
combining the multi-process features into a NEWS entry more closer
to the release, depending on what makes it to the release. Is
that OK with you?
--
Pedro Alves
next prev parent reply other threads:[~2009-04-01 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 14:59 Pedro Alves
2009-03-30 18:42 ` Eli Zaretskii
2009-04-01 23:30 ` Pedro Alves [this message]
2009-04-02 3:15 ` Eli Zaretskii
2009-04-01 23:08 ` 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=200904020030.08885.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--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