Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: Paul Koning <Paul_Koning@dell.com>, gdb@sourceware.org
Subject: Re: RecordReplay: Default answer for changing memory
Date: Wed, 01 Apr 2009 02:43:00 -0000	[thread overview]
Message-ID: <20090401024323.GA8930@adacore.com> (raw)
In-Reply-To: <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


  reply	other threads:[~2009-04-01  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 17:45 Marc Khouzam
2009-03-31 17:51 ` Paul Koning
2009-03-31 18:58   ` Marc Khouzam
2009-04-01  2:43     ` Joel Brobecker [this message]
2009-04-01  3:33       ` Hui Zhu
2009-04-01 17:01       ` Daniel Jacobowitz

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=20090401024323.GA8930@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Paul_Koning@dell.com \
    --cc=gdb@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    /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