This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: MI testsuite improvements
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.
With that, ok.
Andrew
PS: Yes, we need to find a place for explaining how to invoke this.
Looking at the TUI chapter opening there is:
- paragraph stating what TUI is
- paragraph stating how to invoke TUI
MI's chapter should probably do the same.
Any headway on this? Need some more info?
Thanks,
Bob Rossi
@@ -41,6 +41,12 @@
(gdb)
+102-interpreter-exec console "tty /dev/pts/1"
+
+102^done
+
+(gdb)
+
Executing on host: gcc ../../../src/gdb/testsuite/gdb.mi/mi-console.c -DFAKEARGV -g -lm -o /home/bob/cvs/gdb/original/builddir/gdb/testsuite/gdb.mi/mi-console (timeout = 300)
102-break-delete
@@ -128,17 +134,15 @@
(gdb)
-PASS: gdb.mi/mi-console.exp: Started step over hello
-HelloKFAIL: gdb.mi/mi-console.exp: Hello message (PRMS: gdb/623)
- \"!
-
-
+PASS: gdb.mi/mi-console.exp: Testing console output
+Hello \"!
+PASS: gdb.mi/mi-console.exp: inferior_output:Testing console output
47*stopped,reason="end-stepping-range",thread-id="0",frame={addr="0x080483f1",func="main",args=[],file="../../../src/gdb/testsuite/gdb.mi/mi-console.c",line="14"}
(gdb)