This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: RecordReplay: Default answer for changing memory
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Marc Khouzam <marc dot khouzam at ericsson dot com>
- Cc: Paul Koning <Paul_Koning at dell dot com>, gdb at sourceware dot org
- Date: Tue, 31 Mar 2009 19:43:23 -0700
- Subject: Re: RecordReplay: Default answer for changing memory
- References: <6D19CA8D71C89C43A057926FE0D4ADAA072F8043@ecamlmw720.eamcs.ericsson.se> <18898.22572.431889.661694@gargle.gargle.HOWL> <6D19CA8D71C89C43A057926FE0D4ADAA072F8143@ecamlmw720.eamcs.ericsson.se>
> In defaulted_query() GDB bases itself on input_from_terminal_p() and
> figures out that there is no terminal and answers the prompt
> automatically. I'm not exactly sure how to prevent that from
> happening...
The IDE should probably create a pseudo-terminal. That's what GPS
does, as well as what we do when we test GDB (using expect).
Regarding how to prevent this, I posted a patch not too long ago
that proposed the addition of a new setting, off by default, that
would force the debugger to "interactive" mode (it's useful in
the case when running GDB from a "cygwin" window which does NOT
setup a real pseudo-terminal, but rather some pipes). I didn't
feel that there was real interest in this feature, so I figured
no one else was going to use it but me, and only on Windows, so
I droped it.
I really have to agree that Eclipse should be enhanced to allow you
to choose rather than force the default, if that's really the case.
But in the interim, the patch I suggested might be helpful.
http://www.sourceware.org/ml/gdb-patches/2008-10/msg00626.html
--
Joel