From: Karganov Konstantin <kostik@ispras.ru>
To: gdb@sources.redhat.com
Subject: Broken MI output
Date: Thu, 03 Mar 2005 14:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0503031647070.21510-100000@ispserv.ispras.ru> (raw)
Hello.
I tried to run hello-world application under "gdb -i=mi"
and got the following:
-------------------------
~"GNU gdb 6.3\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and you
are\n"
~"welcome to change it and/or distribute copies of it under certain
conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB. Type \"show warranty\" for
details.\n"
~"This GDB was configured as \"i686-pc-linux-gnu\"..."
~"Using host libthread_db library \"/lib/libthread_db.so.1\".\n"
~"\n"
(gdb)
run
&"run\n"
Hello world!
~"Current language: auto; currently c\n"
^done,reason="exited-normally"
(gdb)
-------------------------
Two lines here are out of the grammar syntax: "run" line, that is only
echo of the terminal, that doesnt go out of the debugger (presents only in
debugger stdin) and the " Hello world!" line that is an application output
mixed with MI output. The second line goes out of the debugger stdout and
surely breaks MI-parser.
Am I right that this is a bug ("@ c-string" format is missing) that needs
to be fixed?
Thanks.
Konstantin.
next reply other threads:[~2005-03-03 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 14:17 Karganov Konstantin [this message]
2005-03-03 14:20 ` Bob Rossi
2005-03-03 14:26 ` Karganov Konstantin
2005-03-03 14:34 ` Bob Rossi
2005-03-03 15:02 ` Karganov Konstantin
2005-03-03 15:06 ` Bob Rossi
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=Pine.LNX.4.44.0503031647070.21510-100000@ispserv.ispras.ru \
--to=kostik@ispras.ru \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).