As of now, the debugger output window is not very helpful
for the uninitiated: what is post-prompt supposed to
mean, and what does frames-invalid tell me?
Why not print a complete transscript of the gdb session,
including commands and replies?
This may help gdb newbies to learn gdb, and also it may
help to track down those annoying debugging hangups
that happen every other time with Devcpp.
Logged In: YES
user_id=609236
yes. I think I'm going to create a whole debugger console
where user is going to be able to watch what is going on
behind the scenes, but also enter his/her own commands to
the debugger