From: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/RFC] new setting against auto-answer? (because "input not from terminal")
Date: Sat, 25 Oct 2008 01:41:00 -0000 [thread overview]
Message-ID: <200810250140.m9P1e1ho011456@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: Your message of Fri, 24 Oct 2008 18:04:45 -0700. <20081025010445.GC29038@adacore.com>
> If you have been in that situation, and you use a MinGW debugger,
> then you probably know that there are a few issues with the "terminal".
> One of the issues that is causing us some trouble is the fact that
> GDB automatically assumes the default answer for its y/n queries.
> For instance:
>
> (top-gdb) start
> The program being debugged has been started already.
> Start it from the beginning? (y or n) [answered Y; input not from terminal]
> [...]
>
> I propose a new "set/show interactive-mode (auto|on|off)" command
> to allow the user to override what GDB detects. By default, GDB
> still probes stdin and determines from there what mode should be
> used. But if the user knows what he's doing, he can force it in
> situations where GDB's default behavior is less useful.
If the behavior of GDB on other OS's is OK, shouldn't this be a
configuration parameter of some sort, preferably set automatically by
configure?
Paul Hilfinger
next prev parent reply other threads:[~2008-10-25 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 1:05 Joel Brobecker
2008-10-25 1:41 ` Paul Hilfinger [this message]
2008-10-25 2:00 ` Joel Brobecker
2008-10-25 8:06 ` Eli Zaretskii
2008-10-25 15:46 ` Joel Brobecker
2008-10-25 16:24 ` Daniel Jacobowitz
2008-10-25 17:46 ` Eli Zaretskii
2008-10-26 18:17 ` Joel Brobecker
2008-10-25 13:57 ` Tom Tromey
2008-11-16 8:17 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810250140.m9P1e1ho011456@tully.CS.Berkeley.EDU \
--to=hilfingr@eecs.berkeley.edu \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox