From: ac131313@localhost.cygnus.com (Andrew Cagney)
To: gdb-patches@sources.redhat.com
Subject: [5.1/rfc] Don't print ``(MI_OUT)'' during startup
Date: Sat, 20 Oct 2001 18:23:00 -0000 [thread overview]
Message-ID: <20011021012315.BAE5A3CCD@localhost.cygnus.com> (raw)
Hello,
Given MI is enabled by default, I don't think it makes much sense to
print ``<version> (MI_OUT)''. The attached eliminates that output
and updates the testsuite to match.
Thoughts, if there are no objections, I'll commit it to the 5.1 branch.
enjoy,
Andrew
Index: ChangeLog
2001-10-20 Andrew Cagney <ac131313@redhat.com>
* top.c (print_gdb_version): Do not print ``(MI_OUT)''. MI
interface is always enabled.
Index: testsuite/ChangeLog
2001-10-20 Andrew Cagney <ac131313@redhat.com>
* lib/mi-support.exp (mi_gdb_start): Don't require MI_OUT when
checking MI enabled.
Index: top.c
===================================================================
RCS file: /cvs/src/src/gdb/top.c,v
retrieving revision 1.41.2.1
diff -p -r1.41.2.1 top.c
*** top.c 2001/08/14 20:24:39 1.41.2.1
--- top.c 2001/10/21 01:19:16
*************** print_gdb_version (struct ui_file *strea
*** 1228,1239 ****
program to parse, and is just canonical program name and version
number, which starts after last space. */
- #ifdef MI_OUT
- /* Print it console style until a format is defined */
- fprintf_filtered (stream, "GNU gdb %s (MI_OUT)\n", version);
- #else
fprintf_filtered (stream, "GNU gdb %s\n", version);
- #endif
/* Second line is a copyright notice. */
--- 1228,1234 ----
Index: testsuite/lib/mi-support.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/mi-support.exp,v
retrieving revision 1.8
diff -p -r1.8 mi-support.exp
*** mi-support.exp 2001/06/27 17:27:08 1.8
--- mi-support.exp 2001/10/21 01:19:19
*************** proc mi_gdb_start { } {
*** 117,129 ****
return 1;
}
gdb_expect {
- -re ".*MI_OUT.*$mi_gdb_prompt$" {
- verbose "GDB initialized."
- }
-re ".*$mi_gdb_prompt$" {
! untested "Skip mi tests (output not in headless format)."
! remote_close host;
! return -1;
}
-re ".*$gdb_prompt $" {
untested "Skip mi tests (got non-mi prompt)."
--- 117,124 ----
return 1;
}
gdb_expect {
-re ".*$mi_gdb_prompt$" {
! verbose "GDB initialized."
}
-re ".*$gdb_prompt $" {
untested "Skip mi tests (got non-mi prompt)."
next reply other threads:[~2001-10-20 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 18:23 Andrew Cagney [this message]
2001-10-21 10:10 ` Fernando Nasser
[not found] ` <3BD3057F.8070009@cygnus.com>
2001-10-21 11:16 ` Fernando Nasser
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=20011021012315.BAE5A3CCD@localhost.cygnus.com \
--to=ac131313@localhost.cygnus.com \
--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