From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] gdbserver: qXfer multiprocess
Date: Wed, 17 Jun 2009 00:56:00 -0000 [thread overview]
Message-ID: <h19ev5$puv$1@ger.gmane.org> (raw)
In-Reply-To: <200906162209.37405.pedro@codesourcery.com>
Pedro Alves wrote:
> On Tuesday 16 June 2009 21:10:14, Aleksandar Ristovski wrote:
>
>> This adds check for multiprocess before appending
>> 'multiprocess' to reply.
>
> I can see that from the patch. But, why?
>
If gdbserver doesn't have support for multiple processes,
how will it report lack of that feature to GDB?
I have created gdbserver for nto to be able to use gdb for
nto/linux. One of things this server will not have (at least
for now) is multi process support. It will only handle one
process a time.
--
Aleksandar Ristovski
QNX Software Systems
next prev parent reply other threads:[~2009-06-17 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 20:10 Aleksandar Ristovski
2009-06-16 21:09 ` Pedro Alves
2009-06-17 0:56 ` Aleksandar Ristovski [this message]
2009-06-17 1:04 ` Pedro Alves
2009-06-17 1:17 ` Aleksandar Ristovski
2009-06-17 17:19 ` Aleksandar Ristovski
2009-06-17 18:04 ` Pedro Alves
2009-06-17 19:06 ` Aleksandar Ristovski
2009-06-19 13:41 ` 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='h19ev5$puv$1@ger.gmane.org' \
--to=aristovski@qnx.com \
--cc=gdb-patches@sources.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