From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI testsuite improvements
Date: Thu, 17 Feb 2005 00:28:00 -0000 [thread overview]
Message-ID: <20050216200205.GA6608@white> (raw)
In-Reply-To: <42135BB4.8020506@gnu.org>
On Wed, Feb 16, 2005 at 09:41:56AM -0500, Andrew Cagney wrote:
> Bob Rossi wrote:
>
> >>Let me know what you think. If you want the dbg.log files, I can provide
> >>them.
>
> I was kind of looking for an executive summary :-) I've attached a
> trimmed diff.
>
> Two things:
>
> - it should't be using --interpreter console ...
> Can you and/or: add a new -mi-tty command (+test, +doco) and use that;
> invoke GDB with the --tty=... option. Your call. Either pre-approved
> (but get thumbs up from Eli on the doco).
>
> - can the TTY output be identified in someway?
> That might make debugging easier, but if it isn't possible I guess we
> live with that.
OK, I like this idea a lot. I'll make a new mi function that allows you
to set a tty. I'll also make a new MI function that will allow you to
retrieve the tty device being used, both GDB and the inferior.
Finally, I think it would be helpful to have GDB actually be able to
create a pty for the front end. In case you didn't know, creating a pty
can be a non portable task, and GDB should be capable of doing it every
where it ports to. This would help out the Front Ends a lot. What do you
think? Something like -mi-tty-new -mi-tty-close?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-02-16 20:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 15:43 Bob Rossi
2005-02-10 17:43 ` Andrew Cagney
2005-02-10 18:16 ` Bob Rossi
2005-02-10 19:58 ` Andrew Cagney
2005-02-10 23:34 ` Bob Rossi
2005-02-11 4:01 ` Andrew Cagney
2005-02-11 19:07 ` Bob Rossi
2005-02-12 3:13 ` Andrew Cagney
2005-02-12 10:59 ` Bob Rossi
2005-02-15 15:07 ` Bob Rossi
2005-02-16 20:03 ` Andrew Cagney
2005-02-17 0:28 ` Bob Rossi [this message]
2005-02-17 13:51 ` Daniel Jacobowitz
2005-02-17 16:58 ` Andrew Cagney
2005-02-17 20:09 ` Alain Magloire
[not found] ` <200502171658.LAA02386@smtp.ott.qnx.com>
2005-02-18 2:46 ` Bob Rossi
2005-02-18 12:10 ` Nick Roberts
2005-02-18 19:51 ` Bob Rossi
2005-02-18 21:05 ` Alain Magloire
2005-02-19 23:51 ` Bob Rossi
2005-02-21 2:12 ` Andrew Cagney
2005-02-22 23:24 ` Alain Magloire
[not found] ` <200502221635.LAA07270@smtp.ott.qnx.com>
2005-03-01 2:40 ` Bob Rossi
2005-03-01 15:14 ` Bob Rossi
2005-03-01 19:24 ` Alain Magloire
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=20050216200205.GA6608@white \
--to=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb-patches@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