This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
remote.c:remote_open_1's use of from_tty
- From: Doug Evans <dje at transmeta dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 10 Sep 2002 12:16:41 -0700
- Subject: remote.c:remote_open_1's use of from_tty
I'm trying to decide what the rules are for checking from_tty
when determining whether to print something.
I'm guessing one rule is that when running scripts there is
a preference for them to be quieter than when the same commands
are done interactively. It kinda makes debugging a bit more difficult
though.
Is that the reason for the check for from_tty here?
if (from_tty)
{
puts_filtered ("Remote debugging using ");
puts_filtered (name);
puts_filtered ("\n");
}
Hmmm, after studying it a bit more,
what if we reach the end of a page and the user "quits"?
I don't know remote.c very well but it looks like the target will
be in a half-open state. Am I missing something?