From: Kevin Pouget <kevin.pouget@gmail.com>
To: gdb@sourceware.org
Subject: Multiple remote inferiors
Date: Wed, 06 Apr 2011 15:02:00 -0000 [thread overview]
Message-ID: <BANLkTimVJD8Yq1vyBXzW=1Uz5ea9X=E4Lw@mail.gmail.com> (raw)
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?
it should theoretically be possible, now that multiprocess debugging
has been enabled, so maybe it's because remote.c relies a lot on
global variables?
Cordially,
Kevin
next reply other threads:[~2011-04-06 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 15:02 Kevin Pouget [this message]
2011-04-06 17:44 ` Pedro Alves
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='BANLkTimVJD8Yq1vyBXzW=1Uz5ea9X=E4Lw@mail.gmail.com' \
--to=kevin.pouget@gmail.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