> I take your point that the gdb output is not the world's most easy
> to read; we are trying to improve dbx90 (our front-end to dbx/gdb
> that understands F90) so that it should hopefully be sufficient to
> avoid having to resort to gdb so often in future.
Is there any hope of one with a GUI interface. At least don't require
the input and output to be a terminal, so that I can wrap it in a GUI.
Why was that ever put in in the first place? Why am I prevented from
having a command script that a pipe into the debugger, and why am I
prevented from saving the output to a file? It obviously took some
work, since by default a program will take piped input. Why was this
done?
-jack
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|