From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: Using telnet to control a running GDB
Date: Sun, 28 Nov 2010 22:40:00 -0000 [thread overview]
Message-ID: <201011281736.07476.vapier@gentoo.org> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC572E0C0DCD@EUSAACMS0703.eamcs.ericsson.se>
[-- Attachment #1: Type: Text/Plain, Size: 1308 bytes --]
On Sunday, November 28, 2010 13:27:56 Marc Khouzam wrote:
> I saw a neat feature in another debugger that I thought would be nice for
> GDB.
>
> The user could ask GDB to open a tcp port which would accept a telnet
> connection. Using telnet, the user could then start a _second_ shell to
> the same GDB and control it.
>
> This would help a user get a full-fledge GDB command shell, even when GDB
> is being run by a frontend.
>
> It would also allow the remote controlling of a running GDB. Could be
> useful for troubleshooting.
>
> Such a feature wouldn't already exist, would it?
your description is a bit vague as to what you want this to do exactly. my
understanding of gdb is that it isnt designed for multiple control threads.
plus, it'd be a bit confusing for one gdb controlling a process and to have
two different interfaces attempting to change the execution flow.
ive seen gdb monitors that accepted telnet sessions as well as gdb connections
simultaneously, but the telnet sessions were more for maintenance than actual
gdb type behavior. in other words, you had a dedicated device running a
dedicated monitor that controlled some other processor (e.g. a BDI or PEEDI
ICE).
it'd help if you described with more details and actual examples.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-11-28 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 18:28 Marc Khouzam
2010-11-28 22:40 ` Mike Frysinger [this message]
2010-11-29 2:56 ` Jan Kratochvil
2010-11-29 15:24 ` Marc Khouzam
2010-11-29 18:55 ` Jan Kratochvil
2010-11-29 20:00 ` Marc Khouzam
2010-11-29 20:39 ` Jan Kratochvil
2010-12-06 18:40 ` Tom Tromey
2010-12-06 18:36 ` Tom Tromey
2010-12-07 2:50 ` Marc Khouzam
2010-12-07 15:51 ` Tom Tromey
2010-12-07 16:13 ` Tristan Gingold
2010-12-07 17:14 ` Marc Khouzam
2010-11-29 21:10 ` 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=201011281736.07476.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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