Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: David Taylor <dtaylor@emc.com>
Cc: gdb@sourceware.org
Subject: Re: add-inferior / clone-inferior
Date: Mon, 20 May 2013 15:06:00 -0000	[thread overview]
Message-ID: <519A3BE7.6010004@codesourcery.com> (raw)
In-Reply-To: <7249.1369061005@usendtaylorx2l>

On 05/20/2013 04:43 PM, David Taylor wrote:
> The commands add-inferior / clone-inferior and several related commands
> were added as long ago as gdb 7.1.  But, unless I'm missing the obvious,
> they aren't currently very useful.
>
> GDB appears to support multiple "live" inferiors only when the arise as
> the result of a fork or vfork.  Please tell me that I'm wrong and that
> I'm missing the obvious.
>
>      . I start up gdb with no arguments
>      . file my-elf-file
>      . clone-inferior
>      . info inferiors
>
> I now have two inferiors, numbers 1 and 2, same elf file; 1 is curent.
>
>      . target remote <arguments>
>      . inferior 2
>      . target remote <different-arguments>
>
> And I get:
>
>      A program is being debugged already.  Kill it? (y or n)

This is expected since you can actually have two inferiors, but you are 
only allowed to connect to a single remote target at one time.

What would've worked is first connecting to a remote target in 
*extended* remote mode. Then you would be able to attach to more than a 
process at a time, or start more than a process at a time.

By using "target remote", you're really trying to debug an already 
active process running on a remote system.

I'd suggest reading about the extended remote mode. That looks like what 
you want, though multiprocess support is still a WIP.


  reply	other threads:[~2013-05-20 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 14:43 David Taylor
2013-05-20 15:06 ` Luis Machado [this message]
2013-05-20 15:46   ` David Taylor
2013-05-20 15:52     ` Luis Machado
2013-05-21  1:01 ` Yao Qi
2013-05-21 13:15   ` David Taylor
2013-05-21 13:52     ` Tom Tromey
2013-05-21 14:35       ` David Taylor
2013-05-21 15:46 ` Tom Tromey
2013-05-22 14:47   ` Tom Tromey
2013-05-22 18:21     ` David Taylor
2013-05-22 18:50       ` Tom Tromey
2013-05-22 19:42         ` David Taylor
2013-05-22 20:21           ` Tom Tromey
2013-06-24 20:50   ` Tom Tromey

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=519A3BE7.6010004@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=dtaylor@emc.com \
    --cc=gdb@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