From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Grigory Tolstolytkin <gtolstolytkin@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Extending GDB to provide console over telnet
Date: Fri, 30 Sep 2011 19:27:00 -0000 [thread overview]
Message-ID: <20110930192651.GA8582@host1.jankratochvil.net> (raw)
In-Reply-To: <4E845D53.9090102@gmail.com>
On Thu, 29 Sep 2011 13:58:11 +0200, Grigory Tolstolytkin wrote:
> The idea is to provide users an ability to remotely connect to gdb
> and perform usual debugging interaction while it is already started
> in Eclipse environment via MI interface.
Not sure if you are aware eclipse already provides a window with CLI
interface to running GDB, via MI (also visible in an Eclipse window):
-interpreter-exec console "the-CLI-command-you-entered"
> This allows starting debug locally in Eclipse with connected target
> hardware, for example, and then pass debugging control to a remote
> user at some point.
One can also start gdbserver (even locally):
gdbserver --multi :10000
And use both Eclipse and GDB to attach/detach to that gdbserver using `target
extended-remote' while the inferior is still being debugged:
(gdb) target extended-remote localhost:10000
(gdb) set remote exec-file /home/jkratoch/workspace/entryval2/Debug/entryval2
(gdb) b main
(gdb) run
(gdb) set remote kill-packet off
(gdb) quit
I was able now to attach with Eclipse to a process started using GDB first but
Eclipse killed it during "Detach" but that may be just some Eclipse
configuration setting, I do not know Eclipse much.
Regards,
Jan
prev parent reply other threads:[~2011-09-30 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 11:58 Grigory Tolstolytkin
2011-09-29 12:17 ` Kevin Pouget
2011-09-29 12:42 ` Grigory Tolstolytkin
2011-09-29 12:47 ` Matt Rice
2011-09-30 19:27 ` Jan Kratochvil [this message]
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=20110930192651.GA8582@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=gtolstolytkin@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