From: Nick NoSpam <nicknospam@optonline.net>
To: Bob Rossi <bob@brasko.net>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: MI - Have GDB put pty between it and inferior
Date: Fri, 04 Mar 2005 00:46:00 -0000 [thread overview]
Message-ID: <1109897206.20766.11.camel@nimble.325Bayport> (raw)
In-Reply-To: <20050303143758.GC32613@white>
Take a look at PR 1654.
On Thu, 2005-03-03 at 09:37 -0500, Bob Rossi wrote:
> Hi,
>
> I just had an idea that I got from this Email,
> http://sources.redhat.com/ml/gdb/2005-03/msg00023.html
>
> When GDB is in MI mode, why couldn't it put a pty between the inferior
> and itself. If this happened, it would be possible to direct the output
> of the inferior throught the target stream. Also, it would be possible
> for the front end to send intput to the inferior through an MI command.
>
> Is there any reason this is not a good idea? I'd be happy to look into
> implenting the process, although, creating the pty would be the most
> difficult part since it is highly unportable.
>
> Thanks,
> Bob Rossi
--
Regards,
Nick Gianakas
gianakas@optonline.net
prev parent reply other threads:[~2005-03-04 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 14:38 Bob Rossi
2005-03-04 0:46 ` Nick NoSpam [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=1109897206.20766.11.camel@nimble.325Bayport \
--to=nicknospam@optonline.net \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.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