GDB needs a --cmdline option
Mon May 8 10:10:00 GMT 2000
On Mon, May 08, 2000 at 10:48:21AM -0600, Tom Tromey wrote:
> In invisible mode, gdb would connect its stdin, stdout, and stderr
> directly to the inferior, do whatever initialization it needed, and
> then run the program without user interaction. (The I/O stuff is
> needed because it lets you insert "gdb --invisible" into a pipeline.)
Just as a note, when I was at DG many years ago, the debugger group there added
a feature where a program could invoke the debugger as a child whenever it
wanted to be debugged (usually in the case for long live processes, especially
daemons). I recall some people adding such a call to AOS/VS's equivalent of a
signal handler, so you could just hit ^C to start up the debugger.
I do like the concept of gdb --invisibile. For those of us who greatly prefer
the text interface to a gui interface, you probably want the ability for the
gdb control console to be something other than stdin/stdout.
Michael Meissner, Cygnus Solutions, a Red Hat company.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: firstname.lastname@example.org phone: +1 978-486-9304
Non-work: email@example.com fax: +1 978-692-4482
More information about the Gdb-patches