Hi,
I am using CDT 5.0.0 on Eclipse 3.4.0 on Windows with MinGW 5.1.4.
In console, when i use gdb, I have only a subset of my traces.
Lost lines are: empty lines, lines which begin with '*', '=', ...
e.g. with the following code:
#include <stdio.h>
int main()
{
puts("one");
puts("");
puts("*two");
puts("==>tree");
puts("-->four");
puts("#five");
puts("done");
return 0;
}
on F11 (with gdb), my console shows:
one
-->four
#five
done
on Ctrl+F11 (without gdb), console contents is ok:
one
*two
==>tree
-->four
#five
done
Note 1: my project is a standard project (new>C++ project>Executable>Hello
world c++ project>...)
Note 2: when i activate "verbose console mode" in
"project>properties>run/debug setting>Edit launch configuration>Debugger", i
see all of my traces in gdb traces (see "HERE" tag below)
Any idea ?
Francois.
-----------------------------------------------------------------------------
gdb console:
189-gdb-set confirm off
189^done
(gdb)
190-gdb-set width 0
190^done
(gdb)
191-gdb-set height 0
191^done
(gdb)
192-interpreter-exec console echo
192^error,msg="Undefined MI command: interpreter-exec"
(gdb)
193-gdb-show prompt
193^done,value="(gdb) "
(gdb)
194
&"\n"
194^done
(gdb)
195-gdb-set stop-on-solib-events 0
195^done
(gdb)
196-gdb-set stop-on-solib-events 1
196^done
(gdb)
197-gdb-set new-console off
197^done
(gdb)
198-environment-cd C:\\Dev\\test2
198^done
(gdb)
199-environment-directory C:/Dev/test2 C:/Dev/test2/Debug
C:/Dev/test2/Debug/src C:/Dev/test2/src
199^done
(gdb)
200 info threads
&"info threads\n"
&"No stack.\n"
200^error,msg="No stack."
(gdb)
201-data-list-register-names
201^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs","st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop"]
(gdb)
202-exec-run
202^running <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< HERE
(gdb)
one
*two
==>tree
-->four
#five
done <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< HERE
202*stopped,reason="exited-normally"
(gdb)
203-data-evaluate-expression $_exitcode
203^done,value="0"
(gdb)
204-gdb-exit
204^exit
