Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Kevin Pouget <kevin.pouget@gmail.com>
Subject: Re: Multiple remote inferiors
Date: Wed, 06 Apr 2011 17:44:00 -0000	[thread overview]
Message-ID: <201104061844.01479.pedro@codesourcery.com> (raw)
In-Reply-To: <BANLkTimVJD8Yq1vyBXzW=1Uz5ea9X=E4Lw@mail.gmail.com>

On Wednesday 06 April 2011 16:02:15, Kevin Pouget wrote:
> Hello,
> 
> it looks like it's not possible to connect to several
> remote/extended-remote inferiors at the same time:
> 
> (gdb) target remote :1234
> ...
> (gdb) add-inferior
> Added inferior 2
> (gdb) inferior 2
> [Switching to inferior 2 [process 0] (<noexec>)]
> (gdb) target remote :1235
> A program is being debugged already.  Kill it? (y or n)
> 
> 
> and I was wondering what was the reason?

GDB support multiple processes, but they currently
all need to be behind the same target.

For remote targets, only extended-remote allows that.
E.g., adding a new inferior with add-inferior, switching
to it, and doing "start", should work.

> it should theoretically be possible, 

This is just software, so in theory, anything
is possible.  :-)

> now that multiprocess debugging
> has been enabled, so maybe it's because remote.c relies a lot on
> global variables?

It goes further beyond that.  There's only one target_ops stack.
Going multi-target would be awesome.

-- 
Pedro Alves


  reply	other threads:[~2011-04-06 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 15:02 Kevin Pouget
2011-04-06 17:44 ` Pedro Alves [this message]
2011-04-06 18:50   ` Kevin Pouget
2011-04-06 19:30     ` Pedro Alves
     [not found]       ` <BANLkTinjtiS6cp6WpS=8FULQJdxWuO7K8Q@mail.gmail.com>
2011-04-08  9:43         ` Kevin Pouget
2011-04-08 10:02           ` Jan Kratochvil
2011-04-08 10:00         ` 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=201104061844.01479.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=kevin.pouget@gmail.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