From: florent vion <florent.vion@gmail.com>
To: gdb@sourceware.org
Subject: Debugging Multiple Inferiors
Date: Thu, 07 Sep 2017 12:09:00 -0000 [thread overview]
Message-ID: <CAPkd_ax2i+pR98UXAtEbsE_O4KMs6UQoSzQp7S4Si5v4x7V6=A@mail.gmail.com> (raw)
Hi the experts,
Do you know if it is possible to debug two cortex-m in parallel with
one gdb session using inferiors?
Do I need to enable the non stop mode if I use the remote protocol?
Here my tests so far:
(gdb) target remote :3333
(gdb) file cortex1.elf
(gdb) load cortex1.elf
(gdb) add-inferior
(gdb) inferior 2
(gdb) maint info program-spaces
Id Executable
1 cortex1.elf
Bound inferiors: ID 1 (Remote target)
* 2
Bound inferiors: ID 2 (process 0)
(gdb) target remote :3334
A program is being debugged already. Kill it? (y or n) y
/home/.../gcc-arm/src/gdb/gdb/thread.c:639: internal-error:
thread_info* any_thread_of_process(int): Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
It seems that the remote target behaves as an Highlander, "there can
be only one"...
Regards,
Florent
next reply other threads:[~2017-09-07 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 12:09 florent vion [this message]
2017-09-07 12:50 ` 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='CAPkd_ax2i+pR98UXAtEbsE_O4KMs6UQoSzQp7S4Si5v4x7V6=A@mail.gmail.com' \
--to=florent.vion@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